ci: move the actions/* pins off the Node 20 runtime#12
Merged
Conversation
Runs warn that actions targeting Node 20 are being force-run on Node 24. That fallback is temporary; once it goes the steps fail outright. actions/checkout v4 -> v7 actions/upload-artifact v4 -> v7 actions/download-artifact v4 -> v8 softprops/action-gh-release v2 -> v3 Every input passed here still exists in the target version, checked against each target's action.yml: fetch-depth and ref (checkout), name/path/retention-days (upload-artifact), path/merge-multiple (download-artifact), tag_name/files/generate_release_notes (gh-release). astral-sh/setup-uv and dorny/test-reporter are also on node20 but are left for a separate PR: those cross three and two majors respectively and need their changelogs read, and a regression there should not force a revert of these five. Refs #11 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.
Refs #11 — first of two PRs; deliberately does not close the issue.
Runs warn that actions targeting Node 20 are force-run on Node 24. That fallback is temporary; once GitHub removes it the steps fail outright.
actions/checkoutfetch-depth,refactions/upload-artifactname,path,retention-daysactions/download-artifactpath,merge-multiplesoftprops/action-gh-releasetag_name,files,generate_release_notesInput compatibility was checked by reading each target's
action.ymlat the pinned ref, not assumed from the changelog.Why two PRs
astral-sh/setup-uvanddorny/test-reporterare onnode20too, but they are a different kind of change and follow in a second PR:setup-uvv5 → crosses three majors.test-reporterv1 → crosses two, and it is the action that publishes the check run — a behaviour change there shows up as missing or misattributed test reports, not as a red build.Splitting means a regression in those two does not force a revert of these four.
Verification
All three workflows parse (
YAML.load_file). This PR's own CI exercisescheckoutandupload-artifact;download-artifactandaction-gh-releaseonly run inrelease.ymland stay unproven until the next tag.🤖 Generated with Claude Code