chore(deps): bump the major-updates group across 1 directory with 5 updates

[dependabot]

Bumps the major-updates group with 5 updates in the / directory:

Package	From	To
@systemfsoftware/all	1.1.3	2.1.0
@systemfsoftware/stryker-js-cli	6.0.0	9.0.0
@systemfsoftware/stryker-js-typescript-checker	5.0.0	6.0.0
@systemfsoftware/stryker-js-vitest-runner	4.0.0	5.0.0
@systemfsoftware/stryker-test-contribution	2.0.0	3.0.0

Updates @systemfsoftware/all from 1.1.3 to 2.1.0

Release notes

Sourced from @​systemfsoftware/all's releases.

@​systemfsoftware/all@​v2.1.0

2.1.0

Minor Changes

• The cell-vocabulary rules, including no-io-in-phase-bodies, are no longer part of the preset, because the vocabulary they read was retired with the record-spec authoring surface.

@​systemfsoftware/all@​v2.0.2

2.0.2

Patch Changes

• The recommended oxlint set now carries workflow-variant-constructed and runtime-construction-placement at error, and the make-keyed workflow rules recognize the Workflow.total and Workflow.andThen constructors as lawful workflow construction.

• Updated dependencies:

  • @​systemfsoftware/oxlint-plugin-effect-dmmf@​6.0.0
  • @​systemfsoftware/oxlint-plugin-property-testing@​2.0.0

Commits

• b2ae7d0 chore(release): version packages (#416)
• 825851d refactor(effect-cell-types): honest source resolution, coverage gate, vocabul...
• 68b133e chore(release): version packages (#408)
• f5b6189 chore(release): version packages (#388)
• 5351688 chore(deps): move attw to 4.1.0 and retire its named catalog (#396)
• 47b434a refactor(repo): remove the @​systemfsoftware/source export condition (#392)
• 91dee79 chore(release): version packages (#362)
• ea06bb4 refactor(repo): gate the complexity ceiling, retire the house rule (#381)
• See full diff in compare view

Updates @systemfsoftware/stryker-js-cli from 6.0.0 to 9.0.0

Release notes

Sourced from @​systemfsoftware/stryker-js-cli's releases.

@​systemfsoftware/stryker-js-cli@​v9.0.0

9.0.0

Major Changes

• The plugin system now runs each configured TestRunner/Checker/Reporter plugin in its own spawned process over an @​effect/rpc wire: plugins load from the project's config-declared specifiers (no glob discovery), boundary failures are typed errors, and plugin spans link into the host trace. Breaking: the in-process plugin Layer contract is removed.

• Configuration is now a TypeScript or ECMAScript module — stryker.config.ts, .mts, .js, .mjs, or their stryker.conf.* twins — default-exporting the options object, and --configFile accepts only those extensions. JSON and CommonJS configs are no longer read: when one exists with no supported config file present, the run exits with the config error class naming the file and the supported extensions instead of running on defaults. .ts/.mts load through native type stripping, so a config must be erasable syntax — no enum, runtime namespace, parameter properties, or decorators. Node.js 22.18.0 or later is required (>=22.18.0).

  To migrate, rename the file and convert the JSON object to a default export. From:

  {
    "testRunner": "vitest",
    "mutate": ["src/**/*.ts"]
  }

  to:

  export default {
    testRunner: 'vitest',
    mutate: ['src/**/*.ts'],
  }

Minor Changes

• Exit codes are now published through the runtime's default teardown: interrupt runs exit 130, and classed failures carry their code on the failure. Runs stopped by SIGTERM now exit 130 instead of 143.

• The CLI now exports OpenTelemetry traces when OTEL_ENABLED=true: one stryker.cli.run span per run, annotated with the outcome (stryker.run.outcome), the process exit code (stryker.run.exit_code), and the failure text (stryker.run.error). Spans export over OTLP/HTTP to OTEL_EXPORTER_OTLP_ENDPOINT (default http://127.0.0.1:4318) under OTEL_SERVICE_NAME (default stryker-js); with OTEL_ENABLED unset or false, the CLI emits nothing and takes no exporter dependency at runtime.

Patch Changes

• chore(release): force patch release for @​systemfsoftware/stryker-js-cli via workflow dispatch

Commits

• See full diff in compare view

Updates @systemfsoftware/stryker-js-typescript-checker from 5.0.0 to 6.0.0

Release notes

Sourced from @​systemfsoftware/stryker-js-typescript-checker's releases.

@​systemfsoftware/stryker-js-typescript-checker@​v6.0.0

6.0.0

Major Changes

• The plugin system now runs each configured TestRunner/Checker/Reporter plugin in its own spawned process over an @​effect/rpc wire: plugins load from the project's config-declared specifiers (no glob discovery), boundary failures are typed errors, and plugin spans link into the host trace. Breaking: the in-process plugin Layer contract is removed.

Patch Changes

• Maintenance release. Every published entry point, export, option, and behaviour is exactly as it was.

• effect and typescript dependency ranges widen from exact catalog pins to repo catalog ranges; repository metadata now points at stryker-js-effect

Commits

• See full diff in compare view

Updates @systemfsoftware/stryker-js-vitest-runner from 4.0.0 to 5.0.0

Release notes

Sourced from @​systemfsoftware/stryker-js-vitest-runner's releases.

@​systemfsoftware/stryker-js-vitest-runner@​v5.0.0

5.0.0

Major Changes

• Every module Stryker loads — config files, extends targets, plugins, and the vitest runner's own vitest — now resolves and imports through Node's native ECMAScript module system: import.meta.resolve resolves each bare specifier from the consuming module, and dynamic import() loads the resolved URL. The package's exports map (or a legacy main) selects the entry file, ESM-only plugin packages load, and no require-based loader ships in any package. An unresolvable bare specifier warns with a machine-readable reason; the run fails at prepare only when nothing provides the configured runner or checker. Node.js 22.18.0 or later is required.

  To migrate, install Node.js 22.18.0 or later. Bare plugin specifiers keep working, but a plugin package must publish an ES module entry through exports or main, and the plugin must be resolvable from where Stryker itself is installed.

• The plugin system now runs each configured TestRunner/Checker/Reporter plugin in its own spawned process over an @​effect/rpc wire: plugins load from the project's config-declared specifiers (no glob discovery), boundary failures are typed errors, and plugin spans link into the host trace. Breaking: the in-process plugin Layer contract is removed.

Patch Changes

• Maintenance release. Every published entry point, export, option, and behaviour is exactly as it was.

• effect peer range widens to ^4.0.0-rc.112; repository metadata now points at stryker-js-effect

• The worker environment now arrives on the spawn params instead of mid-init self-mutation, and the setup filename uses a uuid instead of the process id.

Commits

• See full diff in compare view

Updates @systemfsoftware/stryker-test-contribution from 2.0.0 to 3.0.0

Release notes

Sourced from @​systemfsoftware/stryker-test-contribution's releases.

@​systemfsoftware/stryker-test-contribution@​v3.0.0

3.0.0

Major Changes

• The plugin system now runs each configured TestRunner/Checker/Reporter plugin in its own spawned process over an @​effect/rpc wire: plugins load from the project's config-declared specifiers (no glob discovery), boundary failures are typed errors, and plugin spans link into the host trace. Breaking: the in-process plugin Layer contract is removed.

Patch Changes

• Maintenance release. Every published entry point, export, option, and behaviour is exactly as it was.

• the types condition now points at the emitted dist/index.d.ts, the effect peer range widens to ^4.0.0-rc.112, and repository metadata now points at stryker-js-effect

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions