Skip to content

Pin Node to patched releases - #87

Draft
technicalpickles wants to merge 1 commit into
mainfrom
bump-node-patched
Draft

technicalpickles wants to merge 1 commit into
mainfrom
bump-node-patched

Conversation

@technicalpickles

Copy link
Copy Markdown
Owner

Summary

  • Pins Node to 22.23.4 in mise.toml (was floating 22) and in the CI setup-node step (was 20). 22.23.4 is a fixed release for the eMudhra CA compromise, so this repo can't resolve to an older build that still bundles the roots.
  • CI moves from 20 to 22 so it matches the repo's own mise.toml.

Not changed on purpose

The global default in config/mise/conf.d/dotfiles.toml is still node = "lts". Pinning it exactly would change how my global Node tracks LTS (no more automatic moves), so I'd rather decide that separately. Fresh installs of lts resolve to a current release, but an already-installed older LTS stays put until mise upgrade. The fixed releases are 22.23.4, 24.22.1 and 26.12.1.

Test plan

  • mise exec -- npm ci && mise exec -- npm test (typecheck + prettier check) passes on Node v22.23.4.

🤖 Generated with Claude Code

mise.toml 22 -> 22.23.4 and CI 20 -> 22.23.4, per https://emudhra.we-have-a-problem.com/

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant