Update CI actions to Node 24 majors - #10
Merged
Merged
Conversation
devkyato
marked this pull request as ready for review
July 29, 2026 11:05
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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 changed
actions/checkoutfrom v4 to v7actions/setup-pythonfrom v5 to v7actions/upload-artifactfrom v4 to v7Why
The fully successful post-merge 0.2.0 CI run emitted Node 20 deprecation annotations for every job. The official action releases now provide Node 24-based v7 majors, so I am clearing those warnings before tagging the release.
Validation
The preceding 0.2.0 PR and post-merge run passed all ten jobs. This PR intentionally changes only action major pins and the changelog; its own matrix must pass without the Node 20 annotations before merge.