Repository navigation
Conversation
The publish workflow pins actions/setup-python@v2, which runs on the deprecated Node.js 16 runtime and emits deprecation annotations. Bumping to setup-python@v5 (Node 20) removes the warnings; the python-version input and all other step inputs are unchanged.
This branch has not been deployed
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
.github/workflows/python-publish.ymlpinsactions/setup-python@v2.Why
setup-python@v2runs on the Node.js 16 runtime that GitHub has deprecated, so the workflow emits deprecation annotations on every run (checkoutis already on@v4).Change
Bump to
actions/setup-python@v5(Node 20). Thepython-versioninput and all other step inputs are unchanged.One file, one line.