ci: bump workflow actions to latest releases - #7
Merged
Conversation
setup-uv v7 -> v8.3.2 (upstream publishes no floating v8 tag, so pin the exact latest release) and cache v5 -> v6. Both run on node24. checkout, upload-artifact, download-artifact, and gh-action-pypi-publish are already on their latest references.
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
Audits every GitHub Action referenced in the workflows against its latest available release and bumps the two that lag.
astral-sh/setup-uv@v7@v8.3.2v8tag, so pinned to the exact releaseactions/cache@v5@v6actions/checkout@v7actions/upload-artifact@v7actions/download-artifact@v8pypa/gh-action-pypi-publish@release/v1Both upgraded actions run on node24, consistent with the earlier move off deprecated node 20.
Note on the lone pin
setup-uvis the only exact-version pin becauseastral-sh/setup-uvdoes not publish a movingv8major tag (onlyv6,v7, and full releases likev8.3.2). An inline comment documents why. This is also the class of drift that broke CI recently — see the follow-up recommendation to add agithub-actionsDependabot ecosystem.