chore(deps-dev): bump vitest from 4.1.10 to 4.1.11 - #404
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.10 to 4.1.11. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.11/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.11 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
mtskf
added a commit
that referenced
this pull request
Sep 9, 2026
…message - host-session-step.test.ts: fix stale PR #404 reference to the actual PR (#405) that introduced the drain-residue fix - host-session-core.ts: scope the createDrainingDispatcher JSDoc's 'applyEditSettled is the write lock's ONLY release site' claim to a still-alive panel, and note the disposed arm's teardown-only release; correct the citation from edit-settled-barrier.ts (which only consumes isWriteLockHeld) to isWriteLockHeld itself and effect-executor.ts's header - host-session-core.test.ts: assert the AggregateError message string in the multi-throw drain test, which no existing assertion pinned
mtskf
added a commit
that referenced
this pull request
Sep 9, 2026
* fix(host): drain the dispatcher queue to empty when a step throws `createDrainingDispatcher` reset `draining` in a `finally` but neither cleared nor re-drained `queue`, so an event enqueued re-entrantly before a `step` throw sat there until the NEXT external dispatch — a stale replay, arbitrarily later, against a state it was never computed for. Decide the policy explicitly: continue-draining. Each step is caught, the drain runs to an empty queue, and only then does the failure reach the caller — a lone error rethrown as-is (identity and triage payload intact), several as an `AggregateError`. Clearing the queue was rejected because `applyEditSettled` is the write lock's only release site, so dropping one strands the lock and the side channels deferred behind it; documenting the "effects never dispatch synchronously" invariant was rejected because nothing mechanically enforces it. The throw still escapes to the caller, so the unhandled-rejection reasoning in `effect-executor.ts` is unchanged — only its timing moves to the end of the drain; both comments asserting "try/finally and NO catch" are updated. `host-session-step.ts`'s residue baseline test, which asked to be updated consciously if the policy changed, now pins the new one. * fix(host): correct PR ref, scope release-site claim, pin drain error message - host-session-step.test.ts: fix stale PR #404 reference to the actual PR (#405) that introduced the drain-residue fix - host-session-core.ts: scope the createDrainingDispatcher JSDoc's 'applyEditSettled is the write lock's ONLY release site' claim to a still-alive panel, and note the disposed arm's teardown-only release; correct the citation from edit-settled-barrier.ts (which only consumes isWriteLockHeld) to isWriteLockHeld itself and effect-executor.ts's header - host-session-core.test.ts: assert the AggregateError message string in the multi-throw drain test, which no existing assertion pinned
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
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.
Bumps vitest from 4.1.10 to 4.1.11.
Release notes
Sourced from vitest's releases.
Commits
9bd8d46chore: release v4.1.11 (#10995)9851dbcfix(browser): trigger playwright/chromium gc on lower disk availability [back...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 this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.