chore(ci): bump pinned GitHub Actions to Node 24 runtimes#82
Merged
Conversation
GitHub forces Node 20 actions onto the Node 24 runtime on 2026-06-16 and removes the Node 20 runtime entirely on 2026-09-16; the v0.7.0 release run flagged all pinned actions as Node-20-based. Bump every SHA-pinned action across ci.yml, release.yml, and deploy-website.yml to its current major, each verified to declare `using: node24` (upload-pages-artifact is a composite action — bumped for trio-consistency with deploy-pages). actions/checkout v4 -> v6 actions/setup-node v4 -> v6 actions/cache v4 -> v5 pnpm/action-setup v4 -> v6 actions/configure-pages v5 -> v6 actions/upload-pages-artifact v3 -> v5 actions/deploy-pages v4 -> v5 docker/setup-buildx-action v3 -> v4 docker/login-action v3 -> v4 docker/metadata-action v5 -> v6 docker/build-push-action v6 -> v7 softprops/action-gh-release v2 -> v3 All `with:` inputs we pass are unchanged across these majors; pnpm version still resolves from the root packageManager field (pnpm@10.29.3). SHA pins retained (security convention) with refreshed version comments. Co-Authored-By: Claude Opus 4.8 (1M context) <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
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
The v0.7.0 release run flagged every pinned GitHub Action as running on Node.js 20. GitHub forces Node 20 actions onto the Node 24 runtime on 2026-06-16 and removes the Node 20 runtime entirely on 2026-09-16. This bumps all SHA-pinned actions across
ci.yml,release.yml, anddeploy-website.ymlto their current majors — each verified to declareusing: node24via itsaction.yml.Safety
# vNcomments.with:input we pass is unchanged across these majors.pnpm/action-setuptakes noversion:input — it resolves from the rootpackageManagerfield (pnpm@10.29.3), unchanged.using: node24(upload-pages-artifactis a composite action with no Node runtime; bumped for consistency withdeploy-pages).Validation coverage
ci.yml(checkout/pnpm/setup-node/cache) — exercised by this PR's own CI. ✅deploy-website.yml(Pages trio) — its trigger paths include the workflow file, so merging this PR re-runs the website deploy, validating configure-pages/upload-pages-artifact/deploy-pages.release.yml(Docker + gh-release) — only runs on av*tag, so the Docker/release steps are validated at the next release (v0.8.0). Inputs are stable and Node24-verified, so risk is low; worth a glance on the next release run.🤖 Generated with Claude Code