ci: bump pages actions to v5 (Node 24)#93
Merged
Conversation
`actions/deploy-pages@v4` was still emitting the Node 20 deprecation warning after the previous bump. `actions/upload-pages-artifact@v3` is on the same Node 20 runtime even though it wasn''t flagged this run. Bump both to v5.
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
Follow-up to #92. After bumping
actions/checkout,astral-sh/setup-uv, andactions/setup-python, the Node 20 deprecation warning still fired foractions/deploy-pages@v4in the docs-deploy workflow.actions/upload-pages-artifact@v3is on the same runtime even though it wasn''t individually flagged this run.Bumps both to
@v5— release notes fordeploy-pages@v5.0.0explicitly cite "Update Node.js version to 24.x".Test plan
🤖 Generated with Claude Code