ci: upgrade GitHub Pages actions to Node 24 - #18
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
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.
Summary
actions/configure-pagesfrom v5 to v6actions/upload-pages-artifactfrom v4 to v5actions/deploy-pagesfrom v4 to v5Root cause
The first Node 24 migration removed the warning from CI and Release, but the main-branch Pages run exposed three additional Pages actions that still targeted Node 20. The selected official major versions use Node 24;
upload-pages-artifact@v5also embedsactions/upload-artifact@v7.Validation
action.ymlmanifestsgit diff --check