Repository navigation
chore(deps): move vitest and its plugins to 5.0.2 - #5970
Merged
norman-abramovitz merged 5 commits intoSep 29, 2026
Merged
Conversation
Replaces dependabot PR 5963, which moves vitest alone. Vitest 5 peers @vitest/coverage-v8 and @vitest/ui at exactly its own version, so 5963 left both on 5.0.1 against vitest 5.0.2; its CI passed only because the PR checks run neither coverage nor the UI. The three move together here, as in 5b26c1f. Lockfile: the vitest family moves 5.0.1 -> 5.0.2 and vitest's why-is-node-running dependency 2.3.0 -> 3.2.2; nothing else changes.
Vitest 5 peers @vitest/coverage-v8 and @vitest/ui at exactly its own version. Ungrouped, Dependabot opened a vitest-only PR (5963) that passed CI with both plugins still on the old version, since the PR checks run neither coverage nor the UI. The root bun entry now groups vitest and @vitest/* like the Angular packages.
Fragment 0009-vitest-5-0-2 records the three packages moving together and the new Dependabot group.
ANGULAR-21-UPGRADE-STATUS.md was the April 2026 work-in-progress note for an abandoned try/angular-21-upgrade worktree. It describes a unit test blocker (NG0203 under Angular 21 + Vitest 4) that no longer exists, and its versions, resume steps and branches (neither try/angular-21-upgrade nor feature/Angular-21 exists any more) are all out of date. It also carried a local workstation path. Nothing links to it, and it arrived with cloudfoundry#5286 (97d3f33), where the investigation stays in history. The current upgrade procedure lives in docs/build-and-packaging.md.
Fragment 0010-remove-angular-21-status: the file shipped in the repository, so anyone working from a clone sees it disappear.
norman-abramovitz
approved these changes
Sep 29, 2026
norman-abramovitz
left a comment
norman-abramovitz
left a comment
Contributor
There was a problem hiding this comment.
LGTM - approving the changelog fragment that was updated.
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
2 participants
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.
Replaces #5963, which moves
vitestalone. Vitest 5 requires@vitest/coverage-v8and@vitest/uiat exactly its own version, so #5963 would leave both on 5.0.1 againstvitest5.0.2. Its CI passed only because the PR checks run neither coverage nor the UI.vitest@vitest/coverage-v8@vitest/uiscripts/lockdiff.mjs): the Vitest family moves 5.0.1 → 5.0.2, and Vitest'swhy-is-node-runningdependency 2.3.0 → 3.2.2. Nothing else changes; no peer warnings on install.vitestand@vitest/*, as it already does for the Angular packages, so a Vitest-only PR is not proposed again.0009-vitest-5-0-2.Also: stale Angular 21 status document removed
ANGULAR-21-UPGRADE-STATUS.md(repo root) was the April 2026 work-in-progress note for an abandonedtry/angular-21-upgradeworktree. The unit-test blocker it describes (NG0203 under Angular 21 + Vitest 4) no longer exists, the branches it names are gone, and it carried a local workstation path. Nothing linked to it; the investigation stays in history under Angular 21 upgrade (Angular 20 cleanup + Angular 21 + vitest 4) #5286. The current dependency-update procedure is indocs/build-and-packaging.md. Changelog fragment0010-remove-angular-21-status, since anyone working from a clone sees the file go.Verification
make check gategreen on4ba7ab3d4a: 3751 unit tests (2 skipped) under Vitest 5.0.2, noMaxListenersExceededWarning, production build, Go lint and tests across the seven modules.bun run test:coverage: 3751 tests pass with v8 coverage (the path chore(deps-dev): bump vitest from 5.0.1 to 5.0.2 #5963's CI never exercised).vitest --ui: the UI starts and serves its page.