Bump actions/setup-python from v5.6.0 to v6.2.0 (Node 20 → Node 24) - #408
Merged
Merged
Conversation
The v5.x line runs on Node 20, which now emits a deprecation warning in workflow logs. v6.0.0 upgraded the action's runtime to Node 24. Note: setup-python v6+ requires GitHub Actions runner v2.327.1 or later (per upstream release notes).
webknjaz
enabled auto-merge
May 21, 2026 20:57
This was referenced Jul 2, 2026
|
It would be nice if a stable version with this commit could be released... Github has pushed the requirement to nodejs 24 since the beginning of june ! |
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
3 participants
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
action.ymlpinsactions/setup-python@v5.6.0, which uses the Node 20 runtime.v6.2.0(commita309ff8) removes the warning.uses:reference inaction.ymlis the dynamically-generated Docker container action, which is unaffected. Otheractions/checkoutreferences live only in.github/workflows/(this repo's own CI) and are not part of the consumed action.Why the warning surfaces even though the step is skipped
The
Install Python 3step hasif: steps.pre-installed-python.outputs.python-path == '', so it's typically skipped on GitHub-hosted runners (Python is pre-installed). However, the runner still resolves everyuses:reference at workflow start, which is when the Node 20 deprecation warning is emitted — so the warning shows up for consumers regardless. Bumping the pin fixes that.Compatibility note
Per the upstream v6.0.0 release notes,
setup-python@v6requires GitHub Actions runnerv2.327.1or later. GitHub-hosted runners are well past this; self-hosted runner users should verify.