merge queue: embarking main (678ec92) and #1891 together

[mergify]

✨ The merge conditions cannot be satisfied due to failing checks. ✨

Branch main (678ec92) and #1891 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #1891.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule Python Dependency Updates for merge:

• 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

Required conditions to stay in the queue:

• author = renovate[bot]
  • Update dependency uv-build to >=0.11.16 #1891
• check-success = Check Dependency Compatibility
  • Update dependency uv-build to >=0.11.16 #1891
• files ~= ^(uv.lock|pyproject.toml)$
  • Update dependency uv-build to >=0.11.16 #1891
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
    • Update dependency uv-build to >=0.11.16 #1891
  • check-skipped = Mergify Merge Protections
    • Update dependency uv-build to >=0.11.16 #1891
  • check-success = Mergify Merge Protections
    • Update dependency uv-build to >=0.11.16 #1891

---
checking_base_sha: 678ec921875e9f02e5c69e2a67e312b70eda4161
previous_failed_batches: []
pull_requests:
  - number: 1891
    scopes: []
scopes: []
...

[semanticdiff-com]

Review changes with  

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Python dev dependency uv-build to the next patch version and refreshes the lockfile accordingly for a Renovate-driven dependency bump being validated by Mergify’s merge queue.

File-Level Changes

Change	Details	Files
Bump uv-build dev dependency and synchronize the uv.lock lockfile.	Increase the uv-build development dependency minimum version from 0.11.14 to 0.11.15 in the project configuration. Regenerate or update the uv.lock lockfile to reflect the new uv-build version and any transitive resolution changes.	pyproject.toml uv.lock

Possibly linked issues

• #Dependency Dashboard: PR’s uv-build>=0.11.15 change directly corresponds to the uv-build update item in the Renovate dependency dashboard.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[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