chore(ci): move the last two actions onto the Node 24 runtime - #530
Merged
Conversation
GitHub is retiring the Node 20 action runtime, and two pinned actions still declared it: actions/checkout@v4 in the binary-bump check, and actions/setup-python@v5 in the catalog publisher. Every other action in the repo was already on Node 24, so this is the tail of that migration rather than a version bump for its own sake. Verified by reading each pinned version's action.yml, not by inference: ten actions checked, two on node20, and none left after the change.
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 retiring the Node 20 action runtime, and two pinned actions still declared it: actions/checkout@v4 in the binary-bump check, and actions/setup-python@v5 in the catalog publisher. Every other action in the repo was already on Node 24, so this is the tail of that migration rather than a version bump for its own sake.
Verified by reading each pinned version's action.yml, not by inference: ten actions checked, two on node20, and none left after the change.