chore: bump GH Actions to Node 24-compatible releases (Sep 2026 deadline)#7
Merged
Merged
Conversation
…ine) Bumps: - actions/checkout v4 -> v6.0.2 (de0fac2) - actions/setup-node v4 -> v6.4.0 (48b55a0) - actions/upload-artifact v4 -> v7.0.1 (043fb46) - actions/download-artifact v4 -> v7.0.0 (37930b1) - actions/cache v4 -> v5.0.5 (27d5ce7) - actions/github-script v7 -> v9.0.0 (3a2844b) Context: GitHub forces Node 24 default on Jun 2, 2026 and removes Node 20 actions Sep 16, 2026. The v4 (checkout/setup-node/upload/download/cache) and v7 (github-script) pins ran on Node 20. Bumped to latest stable Node 24 releases. download-artifact stays on v7 (v8 changes auto-unzip behavior).
…ad/deploy-pages, etc.) Second pass on the Node 24 transition — first pass covered checkout/setup-node/ upload-artifact/download-artifact/cache/github-script; this pass adds the remaining actions/* that were still on Node 20. Bumps: - actions/setup-python v5 -> v6.2.0 (a309ff8) - actions/upload-pages-artifact v3/v4 -> v5.0.0 (fc324d3) - actions/deploy-pages v4 -> v5.0.0 (cd2ce8f) - actions/configure-pages -> v6.0.0 (45bfe01) [already latest in this org] - actions/setup-dotnet v4 -> v5.2.0 (c2fa09f) - actions/attest-build-provenance v1 -> v4.1.0 (a2bbfa2) - actions/dependency-review-action v4 -> v5.0.0 (a1d282b) All seven moved to Node 24 runtime in their latest stable releases; runner requirement v2.327.1+ is met by github-hosted runners. Breaking-change notes: - upload-pages-artifact v4 excluded hidden dotfiles by default (not _-prefixed paths). Astro/Vite '_astro/' output is unaffected; .well-known/ would be. - attest-build-provenance v2 introduced multi-subject attestation (single attestation per call instead of per-artifact). Backward-compatible for typical single-subject usage. SHA + version-comment pinning convention preserved.
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.
Mechanical sweep ahead of GitHub's Node 24 transition. Node 20 actions emit a deprecation warning today; on Jun 2, 2026 Node 24 becomes the default runtime, and on Sep 16, 2026 Node 20 actions stop working entirely.
Bumps:
actions/checkoutv4 → v6.0.2 (de0fac2e4500dabe0009e67214ff5f5447ce83dd)actions/setup-nodev4 → v6.4.0 (48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e)actions/upload-artifactv4 → v7.0.1 (043fb46d1a93c77aae656e7c1c64a875d1fc6a0a)actions/download-artifactv4 → v7.0.0 (37930b1c2abaa49bbe596cd826c3c89aef350131)actions/cachev4 → v5.0.5 (27d5ce7f107fe9357f9df03efb73ab90386fccae)actions/github-scriptv7 → v9.0.0 (3a2844b7e9c422d3c10d287c895573f7108da1b3)Breaking-change audit:
upload-artifactv5→v7: no breaking changes for typicalname/path/retention-daysusagedownload-artifact: held at v7 rather than v8 — v8 changed default auto-unzip behavior, conservative bump avoids that riskgithub-scriptv9: safe unless any inline script doesrequire('@actions/github')or shadowsgetOctokit— grep across the org showed neither pattern in useSHA + version-comment pinning convention preserved. All pins remain hard-pinned to the commit SHA with a
# vX.Y.Zcomment, matching the org's existing supply-chain hardening style.