ci: bump release workflow actions to Node 24 versions - #52
Merged
Conversation
GitHub deprecated Node 20 actions (forced to Node 24 from 2026-06-16, removed from runners 2026-09-16). Bump the four Node 20 actions in the release workflow to their Node 24 majors, re-pinned to commit SHAs: - actions/create-github-app-token v1 -> v3 - actions/checkout v4 -> v6 (x2) - actions/setup-python v5 -> v6 - crazy-max/ghaction-import-gpg v6 -> v7 git-cliff-action and gh-action-pypi-publish are container-based (not Node), so they are unaffected and left as-is.
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.
Follow-up to #51. The v0.4.0 release logs flagged that four actions in the release workflow still run on Node 20, deprecated by GitHub (forced to Node 24 from 2026-06-16; removed from runners 2026-09-16).
Bumps each to its Node 24 major, re-pinned to a full commit SHA (verified using: node24 in each action.yml):
git-cliff-action and gh-action-pypi-publish are container-based (not Node), so unaffected and left as-is. The create-github-app-token v1->v3 jump keeps the same app-id/private-key inputs and token output, so no other edits needed.
All uses: remain SHA-pinned (satisfies org SHA-pinning policy).