Skip to content

Update the pinned GitHub Actions to their latest releases - #59

Merged
abdullah-bl merged 1 commit into
mainfrom
chore/update-actions
Nov 16, 2026
Merged

abdullah-bl merged 1 commit into
mainfrom
chore/update-actions

Conversation

@abdullah-bl

Copy link
Copy Markdown
Owner

Why

The v0.3.0 release run warned that actions/checkout v4 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.yml still referred to tags (@v4); it is now pinned the same way as the other two.

Action Was Now
actions/checkout v4 v7.0.1
oven-sh/setup-bun v2 v2.2.0 (the same commit)
actions/attest-build-provenance v3 v4.2.2
docker/setup-qemu-action v3 v4.4.0
docker/setup-buildx-action v3 v4.4.1
docker/login-action v3 v4.8.0
docker/build-push-action v6 v7.4.0
actions/configure-pages v5 v6.0.0
actions/upload-pages-artifact v3 v5.0.0
actions/deploy-pages v4 v5.0.1

For each one I read the new action.yml and 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-provenance v4 also writes an "artifact storage record" when push-to-registry is on. That is an organisation API and needs an extra permission; this repository belongs to a user, so create-storage-record: false.
  • upload-pages-artifact v4 and later leave dotfiles out of the artifact. site/dist has a .nojekyll file, so include-hidden-files: true keeps the artifact as it was.

Also worth knowing: actions/checkout v7 refuses to check out a fork's pull request under pull_request_target or workflow_run. None of these workflows use those triggers.

What this PR's checks prove

  • CI runs here with the new checkout and setup-bun pins.
  • Pages runs when this merges to main, because the workflow file changed. That is its first run with the new pins.
  • Release only runs on a tag, so its new pins (the Docker actions and the attestations) are first exercised by the next release.

🤖 Generated with Claude Code

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>
@abdullah-bl
abdullah-bl merged commit c63b59f into main Nov 16, 2026
1 check passed
@abdullah-bl
abdullah-bl deleted the chore/update-actions branch November 16, 2026 02:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants