chore(ci): bump checkout/setup-node to v5 (Node 24 runtime) - #34
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
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.
What
Bumps
actions/checkout@v4 → v5andactions/setup-node@v4 → v5(both now run on Node 24), and the two workflows still pinned to app runtime Node20→22(current LTS).Why
GitHub is force-running Node 20 actions on Node 24 with a deprecation warning (changelog). This clears it for the two actions that have Node 24 majors. Purely mechanical version bumps — no logic changes.
🤖 Generated with Claude Code