Repository navigation
build: update Node.js to v26 and pnpm to v12 - #198
Merged
Merged
Conversation
Pin Node.js 26.10.0 in `.tool-versions` and make every CI job read it. The unit job also runs on Node.js 22, the floor of `engines`, which stays as it is.
Pin pnpm 12.9.1 and ask CI for pnpm 12. Settings need no migration from pnpm 11, and the lockfile already records the `linkDirectory: false` that a frozen install of pnpm 12 checks.
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.
Why
The repository was developed on Node.js 22.18.0 and pnpm 11.9.0, and CI ran on Node.js 22 alone. Node.js 26 is the latest release line and becomes an LTS on 2026-10-28, while the packages keep supporting Node.js 22 until its end of life on 2027-04-30.
pnpm 12 is the latest release, and its breaking changes leave the workspace alone: pnpm 12 recognizes every setting of
pnpm-workspace.yaml, nothing passes--frozen-lockfile false, no dependency comes from git, andengineStrictis off.What
.tool-versionspins Node.js 26.10.0, the latest 26, and pnpm 12.9.1, the version of thelatesttag. Everyactions/setup-nodestep reads Node.js throughnode-version-file, so a bump of the file moves local development and CI together, and everypnpm/action-setupstep asks for pnpm 12.unitjob runs on a matrix of Node.js 22, the floor the packages declare, and the version of.tool-versions.Notes
engines.nodestays>=22in the packages and the root, so nothing gets released. No package depends on@types/node.linkDirectory: falsefor the 8 packages whosepublishConfigsets it, which pnpm 12, like pnpm 11.28, checks in a frozen install.unitcheck now reports asunit (22)andunit (.tool-versions). No branch protection or ruleset requires the old name.minimumReleaseAgehas applied since pnpm 11, so the move to 12 changes nothing about it.pnpm run lint:package-jsonpasses without an install before the script.