Repository navigation
chore(deps): bump Vitest and verify launcher readiness - #129
Conversation
Bumps the testing group with 1 update: [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `vitest` from 5.0.2 to 5.0.3 - [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/v5.0.3/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 5.0.3 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: testing ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
atk0309
changed the title
|
@codex review Review current cumulative head 38401b4. Focus on Vitest 5.0.3 and its intentional why-is-node-running 3.2.1 pin; preserved cumulative dependency and peer records. Earlier updates are preserved for parallel full-tree validation; merges will occur individually in order after checks pass. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Nice work! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
atk0309
changed the title
|
@codex review Review new source head d4d2716. Native Windows test22 exposed a real post-browser startup race. Fresh instance-verified health is checked before existing exit/error guards; a live-unhealthy real-server test requires rejection and full lifetime cleanup. Existing actual OS-exit and healthy-startup cases remain. Verify stop/lock behavior, generic errors, capability secrecy and cumulative dependency integrity. |
|
Codex Review: Didn't find any major issues. Another round soon, please! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
1 participant
Update Vitest from 5.0.2 to 5.0.3 with published transitive changes, retaining upstream's intentional
why-is-node-running3.2.1 pin that fixes pnpm trust-downgrade failures. Preserve preceding Next/Resend updates and supported Node/pnpm pins.Windows native acceptance exposed a launcher race: a worker can exit before Node updates its cached exit state, allowing a false readiness announcement. Recheck bounded, instance-verified HTTP health after browser opening before existing stopped/error/exit guards. Add a real live-unhealthy worker regression requiring startup rejection, worker termination, marker removal and lock release; retain actual-exit and healthy-startup cases.
Validation on reviewed source head
d4d27165dfb87ba0a58b14defc1887b45475097b: full pinned CI passed formatting, lint, types, 1,569 unit tests, build and 32 Chromium cases. Linux and Windows native acceptance passed all real install/browser, archive/license, migration, upgrade/crash/rollback and relaunch checks, including both startup regressions; Windows passed 73 tests. Fresh Codex review found no major issues.Current head
58052b5d1d0a5f1da7ee6fc39b62fdf81a73870eincludes canonical merged main with identical source tree276e691a8eb47370f1ae3e1fe53e33f9881b1236. Fresh current-head CI passed formatting, lint, types, 1,569 unit tests, build and all 32 Chromium cases. Both current-head CodeQL analyses and the aggregate passed. Earlier unstarted Actions cancellation was superseded by these successful analyses. The completed native evidence applies to the unchanged files.