Bump docs workflow actions to Node 24 releases - #3
Merged
Merged
Conversation
Silences the "Node.js 20 is deprecated" CI annotation. - actions/checkout v4 -> v5 - actions/setup-python v5 -> v6 - actions/upload-pages-artifact v3 -> v5 - actions/deploy-pages v4 -> v5 (adds the actions:read permission it now requires) Drop the `.nojekyll` touch: the GitHub Actions Pages deployment serves the artifact statically with no Jekyll step, and upload-pages-artifact v5 strips dotfiles from the artifact anyway. Verified `_static/` assets serve on the live site. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Silences the "Node.js 20 is deprecated" annotation on the Docs workflow.
actions/checkoutactions/setup-pythonactions/upload-pages-artifactactions/deploy-pagesdeploy-pages@v5requires theactions: readpermission — added to thedeployjob.Also drops the
touch .nojekyllstep: the GitHub Actions Pages deployment serves the artifact statically (no Jekyll), andupload-pages-artifact@v5strips dotfiles from the artifact anyway. Confirmed_static/assets serve correctly on the live site.The
buildjob on this PR exercises the newcheckout/setup-python/upload-pages-artifactversions;deploy-pages@v5only runs after merge tomain.🤖 Generated with Claude Code