Repository navigation
Upgrade Vitest while retaining Node 20 CLI support - #95
Open
Ma11hewThomas wants to merge 1 commit into
Open
Ma11hewThomas wants to merge 1 commit into
Ma11hewThomas wants to merge 1 commit into
Conversation
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.
Upgrade Vitest and its matching coverage provider together to 5.0.3. Vitest 5 requires newer development tooling, but the bundled CLI continues to support Node 20.19.0.
CI runs tests/build on a supported tooling version, then switches to each CLI runtime (20/22/24/26) and installs production dependencies only before the existing command smoke checks. Document the development Node requirement in CONTRIBUTING. Package runtime engines and release workflow remain unchanged.
Validation: clean install and full checks on Node 26 pass (79 tests, coverage, build and isolated packed consumers); full/production audits report zero vulnerabilities; 88 registry signatures and 37 attestations verify. All installed/bundled schema copies remain byte-identical to Core. Isolated packed consumers also pass on minimum Node 20.19.0, including both aliases, 0.2.0 validation, historical rejection and no production ctrf package.
Supersedes the separate Vitest and coverage upgrades proposed in #90 and #91.