chore: pin the local toolchain for mise - #247
Merged
Merged
Conversation
`mise install` now gets the node and package manager this repo is developed against, instead of whatever the shell happens to have. The pin mirrors `packageManager` in package.json rather than introducing a second opinion — corepack reads that field, and the two would drift the first time one moved. CI is unaffected: it selects its own node through setup-node and never reads this file. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0163FWV18YYf6AVN3qAd4fYi
|
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.
mise installnow gets the node and package manager this repo is developed against, instead of whatever the shell happens to have.The pin mirrors
packageManagerin package.json rather than introducing a second opinion — corepack reads that field, and two independent declarations would drift the first time one of them moved. Node comes fromengines.nodewhere the repo declares one, floored at 22.CI is unaffected: it selects its own node through setup-node and never reads this file.
Part of a sweep adding the same file across the org.
🤖 Generated with Claude Code
https://claude.ai/code/session_0163FWV18YYf6AVN3qAd4fYi