Update dependency uv-build to >=0.11.22 - abandoned

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
uv-build (source, changelog)	>=0.11.21 → >=0.11.22

---

Release Notes

astral-sh/uv (uv-build)

v0.11.22

Compare Source

Released on 2026-06-18.

Enhancements

• Publish wheels before sdists in uv publish (#​19831)
• Add TY and RUFF env vars for providing paths for binaries used by uv format and uv check (#​19821)

Preview features

• Allow configuring preview features in uv.toml and pyproject.toml (#​18437)
• Update the lockfile during uv check --no-sync (#​19909)
• Add --script to uv check and uv metadata (#​19860)
• Report workspace-exclusive dependency groups in workspace metadata (#​19862)
• Support SARIF as a uv audit output (#​19872)

Performance

• Use a more deadlock-resistant concurrent hashmap in the resolver (#​19532)

Bug fixes

• Update string marker ordering semantics to match upstream clarified rules (#​19808)
• Reject extras that have the same normalized name (#​19871)
• Reject dependency group include-group entries that have additional fields (#​19866)
• Reject invalid UTF-8 URL credentials (#​19814)
• Validate that PEP 517 backend-paths exist when building sdists (#​19834)
• Validate that pylock.toml files do not have an unsupported a lock-version (#​19869)
• Validate that the environment satisfies the packages.requires-python of a pylock.toml (#​19868)
• Allow uv to be recursively invoked by PEP 517 build hooks (#​19879)
• Allow empty credentials.toml files (#​19815)
• Fix transparent Python upgrades in project environments (#​19890)
• Handle non-file editable URLs in uv pip list (#​19867)
• Fix incorrect output from uv tree --invert (#​19910)
• Fix environment locking of uv venv in a project (#​19837)
• Fix handling of workspace-exclusive dependency groups in uv tree (#​19905)

Documentation

• Archive the 0.10.x changelog (#​19813)

Other changes

• Mark more tests as requiring network for vendors that need to run tests offline (#​19819)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-06-20 05:52 UTC · Rule: Python Dependency Updates
• ❌ Checks failed · on draft merge queue: queuing main (3faf315) and #2268 together #2285
• 🚫 Left the queue — 2026-06-20 05:57 UTC · at 9f34d5a4e7ed7853a116d8b391b9e4488d2a1990

This pull request spent 4 minutes 24 seconds in the queue, including 4 minutes 11 seconds running CI.

Waiting for

• check-success = Test Image / API Test

All conditions

• check-success = Test Image / API Test
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections

Reason

The merge conditions cannot be satisfied due to failing checks

Failing checks:

• ❌ Test Image / API Test (job log)

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

[mergify]

Hey @renovate[bot], your pull request has been dequeued due to the following reason: CHECKS_FAILED. Sorry about that, but you can requeue the PR by using @mergifyio requeue if you think this was a mistake.

[renovate]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-06-21 05:00 UTC · Rule: Python Dependency Updates
• ❌ Checks failed · on draft merge queue: queuing main (a8e68fa) and #2268 together #2289
• 🚫 Left the queue — 2026-06-21 05:06 UTC · at b6f6776fb56d442bba9be6d7bc259052b67fa49a

This pull request spent 5 minutes 22 seconds in the queue, including 4 minutes 40 seconds running CI.

Waiting for

• check-success = Test Image / API Test

All conditions

• check-success = Test Image / API Test
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections

Reason

The merge conditions cannot be satisfied due to failing checks

Failing checks:

• ❌ Test Image / API Test (job log)

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Tick the box to put this pull request back in the merge queue (same as @mergifyio queue).

• Requeue this pull request

[mergify]

Hey @renovate[bot], your pull request has been dequeued due to the following reason: CHECKS_FAILED. Sorry about that, but you can requeue the PR by using @mergifyio requeue if you think this was a mistake.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[mergify]

Hi @renovate[bot], Your PR is in conflict and cannot be merged.

[mergify]

👋 renovate[bot] your PR is conflicting and needs to be updated to be merged