Repository navigation
chore: switch to Node.js 24 - #56
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ashirman
approved these changes
Oct 22, 2026
This branch was successfully deployed
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.
Summary
Move the project, its CI and its deploys to Node 24.
Context
Org-wide switch of the pages repos to Node 24. The workflow change mirrors the shared-workflows
pages/template update (revopush/shared-workflowschore/pages-node-24), so the next sync PR should be a no-op.Changes
engines.node:>=22.0.0→>=24.0.0.nvmrc:22→24node-version: '24'How was this tested?
On Node 24.21.0 locally:
pnpm install --frozen-lockfile,pnpm test,pnpm typecheck,pnpm build:preview. Every installed package'sengines.nodeaccepts 24.21.0.🤖 Generated with Claude Code