Repository navigation
chore(deps): bump astral-sh/setup-uv to v10.3.3 - #775
Merged
Merged
Conversation
Co-Authored-By: Matt Quinn <354504+mjq@users.noreply.github.com>
mjq
approved these changes
Nov 12, 2026
3 tasks done
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
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.
Replaces #774.
The
astral-sh/setup-uvpin had a stale# v6comment. The pinned SHA (0a73d6e) and the one #774 bumps to (5e83ccf) are both untagged commits on setup-uvmainafterv10.3.3(git describegivesv10.3.3-5-g0a73d6eandv10.3.3-8-g5e83ccf). Neither is a release. That's likely why Dependabot keeps bumping tomainHEAD instead of release tags.This pins to the
v10.3.3release commit (68559e99cc807c1eb7e9238fd43a15bba460eec2) with a matching# v10.3.3comment, so Dependabot can track tagged releases from here.Notes:
versionandenable-cacheare still valid inputs at v10.3.3.0.13.7. That was added in the untaggeda1b1886. In that case the action checks the download against the checksum from uv's release manifest instead, so the download is still verified.via @mjq.
--
View Session [Sentry]