chore: move the pinned actions off Node 20 - #19
Merged
Conversation
GitHub is forcing Node-20 actions onto Node 24, which surfaces as a deprecation warning on every run: Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/upload-artifact@ea165f8d... Bumps the three pins that still shipped `runs.using: node20`: upload-artifact v4 -> v7.0.1 (043fb46d) download-artifact v4 -> v8.0.1 (3e5f45b2) setup-node v4 -> v7.0.0 (82076278) checkout was already on v6/node24 and is unchanged. Note that upload-artifact v5 does NOT fix this — v5 kept node20 as its default runtime and only had preliminary node24 support. v6 is the first release that actually runs on node24, and the same applies to download-artifact v7. upload-artifact v6+ and download-artifact v7+ require Actions Runner >= 2.327.1. The Shiplight self-hosted runners report 2.336.0, so this is safe; a consumer on older self-hosted runners would need to update them first. Two behaviour changes ride along with the majors, both wanted here: - download-artifact v8 errors on a digest mismatch rather than warning. For a pipeline that diagnoses failures from a downloaded report, failing loudly on a corrupt artifact beats silently reasoning about garbage. - Both actions moved to ESM, which is transparent to callers. Every `with:` block was checked against the new input sets; all five usages are still valid. Co-Authored-By: Claude Opus 5 (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.
GitHub is forcing Node-20 actions onto Node 24, warning on every consumer run.
043fb46d)3e5f45b2)82076278)checkoutwas already on v6/node24.upload-artifact@v5would not have fixed this — v5 kept node20 as its default runtime and only had preliminary node24 support. v6 is the first that actually runs node24; same for download-artifact v7.v6+/v7+ require Actions Runner >= 2.327.1. The Shiplight self-hosted runners report 2.336.0, so this is safe. Consumers on older self-hosted runners must update first — worth knowing before upgrading.
One behaviour change rides along:
download-artifact@v8errors on a digest mismatch rather than warning. For a pipeline that diagnoses failures from a downloaded report, failing loudly on a corrupt artifact beats reasoning about garbage.Every
with:block was validated against the new input sets; all five usages remain valid.🤖 Generated with Claude Code