Repository navigation
Move Pages configuration to the Node 24 action runtime - #63
Merged
Merged
Conversation
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.
Why
The Pages workflow still pinned actions/configure-pages to a 2024 commit that targets Node.js 20. GitHub now emits a deprecation warning and forcibly runs that action on Node.js 24.
Change
Pin actions/configure-pages v6.0.0 by its immutable, verified commit SHA. The action declares runs.using: node24.
Verification
The PR must pass CI, CodeQL, and the use-cases-site build before merge. After merge, the main-branch Pages deployment will be checked explicitly.