fix(deps): bump uv lower bound to >=0.11.6 for GHSA-pjjw-68hj-v9mw#622
Merged
olivermeyer merged 2 commits intoMay 4, 2026
Merged
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
olivermeyer
requested a review
from helmut-hoffer-von-ankershoffen
as a code owner
…main The uv-lock hook updated uv.lock in the previous commit, which introduced a new conflict with main's uv.lock. The original release branch lock auto-merges cleanly with main, so we restore it here. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
dima-aignostics
approved these changes
May 4, 2026
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.
Why?
PR #620 (
release/v1.3.0→main) is blocked by a merge conflict caused bymainbumpinguvto>=0.11.6(fixing GHSA-pjjw-68hj-v9mw) after the release branch was cut.How?
Applies the same
uv>=0.11.6lower bound and extended CVE comment torelease/v1.3.0directly, so both sides of the merge become identical and git resolves the conflict automatically.