Skip to content

[codex] Pin project runtime to Node 22 - #427

Open
Dreamstore2046 wants to merge 1 commit into
harystyleseze:mainfrom
Dreamstore2046:codex/careguard-node-22-policy-231
Open

[codex] Pin project runtime to Node 22#427
Dreamstore2046 wants to merge 1 commit into
harystyleseze:mainfrom
Dreamstore2046:codex/careguard-node-22-policy-231

Conversation

@Dreamstore2046

Copy link
Copy Markdown

Summary

  • add root engines.node policy for Node.js >=22.0.0
  • add .nvmrc with 22 for local development
  • update remaining GitHub Actions setup-node steps from Node 20 to Node 22
  • document the Node 22 policy in CONTRIBUTING.md
  • refresh package-lock.json so the root package metadata matches package.json

Closes #231

Validation

  • npm install --package-lock-only --ignore-scripts --legacy-peer-deps
  • node -e "const fs=require('fs'); const pkg=JSON.parse(fs.readFileSync('package.json','utf8')); const lock=JSON.parse(fs.readFileSync('package-lock.json','utf8')); if(pkg.engines.node!=='>=22.0.0') throw new Error('package engines mismatch'); if(lock.packages[''].engines.node!=='>=22.0.0') throw new Error('lock engines mismatch'); console.log('node engines pinned to '+pkg.engines.node);"
  • rg "node-version:\\s*['\\\"]?20|node-version:\\s*20|node-version:\\s*\\\"20\\\"|node-version:\\s*'20'" .github/workflows (no matches)
  • git diff --cached --check

@vercel

vercel Bot commented Jun 26, 2026

Copy link
Copy Markdown

@Dreamstore2046 is attempting to deploy a commit to the Harrison Eze's projects Team on Vercel.

A member of the Team first needs to authorize it.

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.

No engines.node in package.json — Node 20 vs 22 drift

1 participant