Bump publish workflow actions off deprecated Node 20 - #18
Merged
Conversation
checkout@v4->v5, setup-uv@v5->v7, upload-artifact@v4->v7, download-artifact@v4->v8 — the majors whose action.yml declares node24 (verified; the next-major bump wasn't enough — setup-uv@v6 / artifact@v5 are still node20).
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.
The PyPI publish workflow ran with Node-20 deprecation warnings. Bump the four flagged actions to the majors whose
action.ymldeclares node24 (verified via each tag's runtime — the naive next-major wasn't enough:setup-uv@v6andartifact@v5are still node20):actions/checkout@v4→ @v5astral-sh/setup-uv@v5→ @v7actions/upload-artifact@v4→ @v7actions/download-artifact@v4→ @v8upload@v7/download@v8share the v4-era immutable-artifact backend, so they pair.pypa/gh-action-pypi-publish@release/v1wasn't flagged (moving tag, maintained). Workflow-only; publish runs only on release, so this doesn't re-trigger a publish.