ci: upgrade softprops/action-gh-release to v3 (Node 24 runtime) - #25
Merged
Conversation
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.
What
Bumps
softprops/action-gh-releasefrom@v2to@v3in.github/workflows/release.yml(the "Create GitHub Release" step).Why
The v0.10.21 release run surfaced a deprecation annotation:
softprops/action-gh-releasev3.0.0 moved the action runtime from Node 20 to Node 24 (action.ymlnow declaresruns.using: "node24"). Thev2floating tag is intentionally pinned to the last Node 20 line by the maintainer, so it will keep emitting this deprecation. Moving tov3(currently v3.0.2) resolves it.Notes
generate_release_notesandfilesare still supported, so no other edits are needed.ubuntu-latest(GitHub-hosted), which already runs the Node 24 Actions runtime, sov3is safe.@v3, consistent with the repo's other actions (actions/checkout@v5,actions/upload-artifact@v6,actions/download-artifact@v7).Verification
CI runs on release tags, so this is exercised by the next version tag push. No functional change to the release contents.