ci: bump actions off the deprecated Node 20 runtime - #20
Merged
Merged
Conversation
GitHub is force-running Node 20 actions on Node 24 and will drop the shim; every build job currently emits a deprecation annotation. - actions/checkout v4 -> v7 - actions/upload-artifact v4 -> v7 - actions/download-artifact v4 -> v8 - softprops/action-gh-release v2 -> v3 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HDpmynESrQrqCCKMuWNgYk
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.
Every job in
Build Spatial Protocol Mappercurrently emits:The compatibility shim is temporary, so these bumps get us off it before it disappears.
Changes (
.github/workflows/build.yml)actions/checkoutactions/upload-artifactactions/download-artifactsoftprops/action-gh-releaseaction-gh-release@v2is also pinned to Node 20 (v3 is the Node 24 line), it just wasn't surfaced in the annotations because the release job only runs onmain/tags.Breaking changes reviewed
All of these majors carry breaking-change notes; none affect this workflow:
pull_request_target/workflow_run. This workflow uses plainpull_request, so it's unaffected. v5/v6 were Node 24 + credential-storage changes.archive: falsedirect-upload mode. Default stays zipped, so the upload/download pairing is unchanged.pattern: app-*withmerge-multiple: true, which was explicitly called out as unaffected.digest-mismatchnow defaults toerrorinstead of a warning. That's a stricter integrity check on artifact download; it should only fire on genuine corruption, and erroring is the behaviour we want for release artifacts.Hosted runners only (
ubuntu/macos/windows-latest), so the ≥2.327.1 runner-version requirement of the Node 24 majors is already satisfied.Not covered
jcelerier/import-codesign-certs@masteralso shows in the macOS annotations, but it's pulled in byossia/actions/custom-score-build, not by this repo — it has to be fixed upstream inossia/actions..github/workflows/claude.ymlstays onactions/checkout@v6, which is already Node 24 and not deprecated.Verification
This PR exercises
checkout@v7andupload-artifact@v7on all four platforms. Thereleasejob is gated on tags/main, sodownload-artifact@v8andaction-gh-release@v3won't run until this lands onmain— the continuous release upload is the first real test of those two.🤖 Generated with Claude Code
https://claude.ai/code/session_01HDpmynESrQrqCCKMuWNgYk