chore(deps-dev): bump the stryker group with 2 updates#22
Merged
Conversation
Bumps the stryker group with 2 updates: [@stryker-mutator/core](https://github.com/stryker-mutator/stryker-js/tree/HEAD/packages/core) and [@stryker-mutator/vitest-runner](https://github.com/stryker-mutator/stryker-js/tree/HEAD/packages/vitest-runner). Updates `@stryker-mutator/core` from 9.6.0 to 9.6.1 - [Release notes](https://github.com/stryker-mutator/stryker-js/releases) - [Changelog](https://github.com/stryker-mutator/stryker-js/blob/master/packages/core/CHANGELOG.md) - [Commits](https://github.com/stryker-mutator/stryker-js/commits/v9.6.1/packages/core) Updates `@stryker-mutator/vitest-runner` from 9.6.0 to 9.6.1 - [Release notes](https://github.com/stryker-mutator/stryker-js/releases) - [Changelog](https://github.com/stryker-mutator/stryker-js/blob/master/packages/vitest-runner/CHANGELOG.md) - [Commits](https://github.com/stryker-mutator/stryker-js/commits/v9.6.1/packages/vitest-runner) --- updated-dependencies: - dependency-name: "@stryker-mutator/core" dependency-version: 9.6.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: stryker - dependency-name: "@stryker-mutator/vitest-runner" dependency-version: 9.6.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: stryker ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Deploying fs-packages with
|
| Latest commit: |
bea594f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://749db398.fs-packages.pages.dev |
| Branch Preview URL: | https://dependabot-npm-and-yarn-stry.fs-packages.pages.dev |
Goosterhof
added a commit
that referenced
this pull request
May 8, 2026
Add an Authentication & XSRF section to docs/packages/http.md sibling- level to the Doctrine #8 Timeout block, naming Laravel Sanctum SPA explicitly, explaining the XSRF-TOKEN cookie + axios 1.x withXSRFToken mechanics, and stating the HTTP 419 failure mode (which mocked transports do not surface, per ADR-0017). Stateless / token / non- Sanctum stacks documented as the inverse case. Expand the API Reference row for options.withXSRFToken with the same guidance and a cross-link to the new section. Add a one-line README pointer mirroring the Timeout pointer shape landed by Engineer PR #68 (no full duplication; docs page is source of truth). Closes enforcement queue #22 docs path. Commander disposition: docs- only. Library default of withXSRFToken: false stays as-is. No oxlint call-site rule. No source code changes. No version bump. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
jasperboerhof
added a commit
that referenced
this pull request
May 12, 2026
…sanctum-docs docs(http): Sanctum XSRF gotcha — closes queue #22 docs path
jasperboerhof
pushed a commit
that referenced
this pull request
May 20, 2026
Removes streamRequest entirely: source, type signature, tests, docs. Closes enforcement queue #64 (XSRF bypass) and the streamRequest portion of queue #22 in one structural stroke; also closes Surveyor M3 findings F-1 (headers ignored) and F-2 (timeout ignored). Supersedes PR #86. streamRequest was a parallel transport built on native fetch that bypassed the option-honoring discipline the axios-routed methods inherit from axios.create(). Four documented library-invariant violations had accumulated on its option-honor surface (headers, withXSRFToken, withCredentials — withCredentials was fixed in 0.3.0, the others remained). Zero realized consumers across the war-room fleet (Engineer + Sapper M3 + Liaison M3 grep convergence) — every per-defect fix was a band-aid on a parallel- transport divergence. Removal closes all four queue rows. Mock objects in fs-loading and fs-cached-adapter-store tests dropped their streamRequest: vi.fn() entries to keep the HttpService type contract honest. The docs page download/preview API Reference rows were corrected to the 0.3.0 signature in the same pass (Warden M2 standing drift). Surveyor M3 field report: reports/fs-packages/field/2026-05-15-surveyor-library-config-honor-surface-audit.md Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Goosterhof
added a commit
that referenced
this pull request
May 29, 2026
Removes streamRequest entirely: source, type signature, tests, docs. Closes enforcement queue #64 (XSRF bypass) and the streamRequest portion of queue #22 in one structural stroke; also closes Surveyor M3 findings F-1 (headers ignored) and F-2 (timeout ignored). Supersedes PR #86. streamRequest was a parallel transport built on native fetch that bypassed the option-honoring discipline the axios-routed methods inherit from axios.create(). Four documented library-invariant violations had accumulated on its option-honor surface (headers, withXSRFToken, withCredentials — withCredentials was fixed in 0.3.0, the others remained). Zero realized consumers across the war-room fleet (Engineer + Sapper M3 + Liaison M3 grep convergence) — every per-defect fix was a band-aid on a parallel- transport divergence. Removal closes all four queue rows. Mock objects in fs-loading and fs-cached-adapter-store tests dropped their streamRequest: vi.fn() entries to keep the HttpService type contract honest. The docs page download/preview API Reference rows were corrected to the 0.3.0 signature in the same pass (Warden M2 standing drift). Surveyor M3 field report: reports/fs-packages/field/2026-05-15-surveyor-library-config-honor-surface-audit.md Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Bumps the stryker group with 2 updates: @stryker-mutator/core and @stryker-mutator/vitest-runner.
Updates
@stryker-mutator/corefrom 9.6.0 to 9.6.1Release notes
Sourced from
@stryker-mutator/core's releases.Changelog
Sourced from
@stryker-mutator/core's changelog.Commits
e1abfbev9.6.11f68437fix(deps): update mutation-testing-elements monorepo to v3.7.3 (#5912)5a24298fix(deps): update dependency typed-rest-client to ~2.3.0 (#5933)6792b90chore(deps): update dependency@types/nodeto v24.12.2 (#5943)be5a1b8chore(deps): update dependency@types/nodeto v24.12.1 (#5942)a990813chore(deps): update dependency@types/nodeto v24.12.0 (#5887)e511114chore(deps): update dependency@types/nodeto v24.11.2 (#5885)9d2bb9achore(deps): update dependency@types/nodeto v24.11.0 (#5879)e634c9achore(deps): update dependency@types/nodeto v24.10.15 (#5871)2834eb5chore(deps): update dependency@types/nodeto v24.10.14 (#5870)Updates
@stryker-mutator/vitest-runnerfrom 9.6.0 to 9.6.1Release notes
Sourced from
@stryker-mutator/vitest-runner's releases.Changelog
Sourced from
@stryker-mutator/vitest-runner's changelog.Commits
e1abfbev9.6.1f421b42chore(deps): update dependency vite to v7.3.2 (#5949)56c1ae2fix(vitest-runner): fix vitest runner mutant hitcount and coverage for v4.1 (...1a30329chore(deps): update dependency vitest-browser-react to v2.2.0 (#5947)6792b90chore(deps): update dependency@types/nodeto v24.12.2 (#5943)be5a1b8chore(deps): update dependency@types/nodeto v24.12.1 (#5942)f29da0echore(deps): update dependency vitest-browser-react to v2.1.0 (#5906)a990813chore(deps): update dependency@types/nodeto v24.12.0 (#5887)e511114chore(deps): update dependency@types/nodeto v24.11.2 (#5885)9d2bb9achore(deps): update dependency@types/nodeto v24.11.0 (#5879)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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