Bump actions/setup-python from v5 to v6 (Node.js 24)#4
Merged
Conversation
v5 runs on Node.js 20, which GitHub will force to Node.js 24 by default on 2026-06-02 and remove on 2026-09-16. v6 ships on Node.js 24 with the same input/output API.
1 task
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.
Summary
actions/setup-pythonfromv5tov6so this action stops triggering the Node.js 20 deprecation warning.action.yml—python-versionand the rest of the inputs we use are unchanged).python-versioninput description to match.Why now
GitHub will force Node.js 20 actions to Node.js 24 by default on 2026-06-02 and remove Node.js 20 from runners entirely on 2026-09-16 (changelog). Consumers of
xonsh/actions@v1are currently surfacing a deprecation warning sourced from the pinnedsetup-python@v5.Test plan
setup-python@v6and installs xonsh successfully.