Repository navigation
CI: move workflow actions to their Node 24 releases - #6899
Merged
Merged
Conversation
GitHub now forces Node 20 actions onto Node 24 and warns on every run. Bump configure-pages, upload-pages-artifact (which pulls in upload-artifact v7), deploy-pages, setup-node and the old checkout v3. upload-pages-artifact v4+ skips hidden files; the built site has none. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅ Deploy Preview for prebid-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
ChrisHuie
approved these changes
Oct 31, 2026
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
Every docs workflow run ends with a warning that Node.js 20 is deprecated and that some actions are being forced to run on Node.js 24 (for example
actions/configure-pages@v5andactions/upload-artifact@v4). This updates those actions to releases built for Node 24.Changes
pages-deploy.ymlactions/configure-pagespages-deploy.ymlactions/upload-pages-artifactupload-artifactv7)pages-deploy.ymlactions/deploy-pagesci.ymlactions/setup-nodecode-path-changes.ymlactions/checkoutcode-path-changes.ymlactions/setup-nodeThings checked
upload-pages-artifactv4 and later leave hidden files (dotfiles) out of the Pages artifact. The current site artifact contains none, so nothing is dropped.code-path-changes.ymlstill installs Node 18 for its notification script. That's unchanged here and could be bumped separately.master, so it's verified by the first deploy after merging: check that the run shows no Node 20 warning and that docs.prebid.org still serves/pagefind/pagefind-component-ui.jswith a 200.🤖 Generated with Claude Code