Use Node 24 for Pages deployment - #38
Merged
Merged
Conversation
jmchilton
marked this pull request as ready for review
August 4, 2026 12:58
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.
What changed
withastro/action@v3to build the Pages site with Node 24Why
The Pages deployment still used the action's Node 20 default. The site now requires Node
>=22.12.0, and Astro 7.1.6 refuses to build under Node 20. The post-merge deployment failed before Astro could render any pages.Node 24 matches the toolchain documented by the project and satisfies both the site's engine constraint and Astro's supported range.
Impact
GitHub Pages builds use the same supported Node major expected by the repository. No site source or generated output changes.
Validation
npm cinpm run buildnpm test— 22 passednpm run typecheck— no errors; one existing unused-variable hintgit diff --checkFixes the failure in Pages run 30909495844.