deps: update devDependencies and Node.js toolchain#65
Merged
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
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.
What
Refresh the dev toolchain for the June update cycle, including Node.js, pnpm metadata, and several devDependencies. This also updates the lockfile to the newly resolved dependency graph.
Why
Keep the build and test toolchain current, pick up upstream fixes in the development stack, and align the repo with the latest pnpm and Node.js versions used by this branch.
How
Bump the Node.js version in
.nvmrc, update the affected devDependencies andpackageManagerfield inpackage.json, then regenerate the lockfile. AddminimumReleaseAgeExcludeentries inpnpm-workspace.yamlso the updatedarktypedependency set remains installable under pnpm release-age policy.Changes
.nvmrcfromv24.15.0tov24.16.0package.json, including Biome, Node types, tsdown, vite, vitest, and related packagespackageManagertopnpm@11.7.0pnpm-lock.yamlarkregex@0.0.6andarktype@2.2.1Testing
pnpm run ciDeployment
v24.16.0.pnpm@11.7.0and the workspace release-age exclusions inpnpm-workspace.yaml.