Repository navigation
fix: Upgrade uv to 0.13.4 for the eMudhra CA compromise - #90
Merged
Merged
Conversation
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
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.
ENG-9339
what
Bump the uv pin in
.tool-versionsfrom 0.12.23 to 0.13.4. The CIand release workflows read this pin to install uv.
why
uv 0.13.4 is the first fixed release for the eMudhra CA compromise.
The epic ENG-9331 has the detail.
testing
CI installs uv from this pin, so the CI run on this PR exercises
uv syncand the test suite with 0.13.4 against the currentuv.lock.docs
No docs needed.
🤖 Generated with Claude Code