chore(ci): CI and .nvmrc follow the box to Node 24 - #860
Merged
Conversation
The box ran Node 20 four months past EOL; it moved to 24.20.0 today with every service health-verified. CI validating on 20 now validates against a runtime nothing uses. The npm-audit gate's node/npm coupling comment told the bumper to re-check its exit code first (npm 11 stops honoring --audit-level): re-checked on npm 11.11 — the tree is clean at every level, exit 0 — and the comment now records that instead of still claiming node 20. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WqKqMnHQHSmkGFfc5t7Rxn
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.
The box (bitbaum) moved from Node 20 (four months past EOL) to 24.20.0 today, every service health-verified. This aligns CI and .nvmrc with the runtime that actually serves production.
node-version: 20->24in ci.yml (3 pins), cd.yml, e2e-auth.yml.nvmrc20 -> 24--audit-level): re-checked on npm 11.11 —npm audit --omit=dev --jsonreports 0 vulnerabilities at every level, exit 0. The comment now records that instead of still claiming node 20.No
engineschanges. Config-only; CI on this PR is the verification.🤖 Generated with Claude Code
https://claude.ai/code/session_01WqKqMnHQHSmkGFfc5t7Rxn