Repository navigation
Use current official Node 24 Pages actions - #5
Merged
Merged
Conversation
ThorFuchs
changed the title
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 initial Pages deployment exposed deprecated Node 20 action runtimes. Pin the current official upload-pages-artifact v5, configure-pages v6 and deploy-pages v5.0.1 releases, all of which use Node 24. Explicitly retain the verified .nojekyll file in the site artifact.
The library, documentation content, consumers and benchmarks are unchanged. All protected native, safety and documentation checks must pass; publication remains restricted to main after those checks.