chore: Update GitHub Actions to v6 for Node 24 support #239
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
Update actions/checkout and actions/setup-python from v4 to v6 to prepare for the upcoming Node 20 deprecation on GitHub Actions runners. Node 20 will reach EOL in April 2026, and GitHub Actions will migrate to Node 24 by default starting March 4th, 2026. Reference: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
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.
Summary
Updates
actions/checkoutandactions/setup-pythonfrom v4 to v6 to prepare for the upcoming Node 20 deprecation on GitHub Actions runners.Context
I noticed that the recent release (merged in PR #235) pinned the GitHub Actions to v4 with SHA hashes. However, Node 20 is being deprecated on GitHub Actions:
Changes
actions/checkout08eba0b27e820071cde6df949e0beb9ba4906955)8e8c483db84b4bee98b60c0593521ed34d9990e8)actions/setup-python7f4fc3e22c37d6ff65e88745f38bd3157c663f7c)83679a892e2d95755f2dac6acb0bfd1e9ac5d548)Why Node 24?
I would highly encourage moving to Node 24. According to the GitHub blog post:
Beginning on March 4th, 2026, runners will begin using Node 24 by default. Updating to v6 of these actions ensures compatibility with Node 24 and avoids any potential issues when the deprecation takes effect.
Reference