Repository navigation
Update the pinned GitHub Actions to their latest releases - #59
Merged
Merged
Conversation
The v0.3.0 release run warned that actions/checkout v4 targets Node.js 20, which GitHub now forces onto Node.js 24. Every action moves to its newest release, pinned to that release's commit, and pages.yml (which still used tags) is pinned the same way. Two of the new versions change a default, and each is set back to what the workflows did before: - attest-build-provenance v4 also writes an artifact storage record when it pushes to the registry. That is an organisation feature and this repository belongs to a user, so it is turned off. - upload-pages-artifact v4 and later leave dotfiles out; site/dist has a .nojekyll file, so include-hidden-files keeps the artifact as it was. Co-Authored-By: Claude Fable 5.2 <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.
Why
The v0.3.0 release run warned that
actions/checkoutv4 targets Node.js 20, which is deprecated and is being forced onto Node.js 24.What
Every action in the three workflows moves to its latest release, pinned to that release's commit.
pages.ymlstill referred to tags (@v4); it is now pinned the same way as the other two.actions/checkoutoven-sh/setup-bunactions/attest-build-provenancedocker/setup-qemu-actiondocker/setup-buildx-actiondocker/login-actiondocker/build-push-actionactions/configure-pagesactions/upload-pages-artifactactions/deploy-pagesFor each one I read the new
action.ymland the release notes of every major version in between: all the inputs and outputs these workflows use still exist, and the node-based ones run on Node.js 24.Two defaults that changed
Both are set back to what the workflows did before:
attest-build-provenancev4 also writes an "artifact storage record" whenpush-to-registryis on. That is an organisation API and needs an extra permission; this repository belongs to a user, socreate-storage-record: false.upload-pages-artifactv4 and later leave dotfiles out of the artifact.site/disthas a.nojekyllfile, soinclude-hidden-files: truekeeps the artifact as it was.Also worth knowing:
actions/checkoutv7 refuses to check out a fork's pull request underpull_request_targetorworkflow_run. None of these workflows use those triggers.What this PR's checks prove
checkoutandsetup-bunpins.main, because the workflow file changed. That is its first run with the new pins.🤖 Generated with Claude Code