merge queue: checking main (f33bbb0) and #2838 together

[mergify]

⏳ The pull request #2838 is queued for merge and currently being checked. ⏳

Branch main (f33bbb0) and #2838 are queued together for merge.

This pull request has been created by Mergify to check the mergeability of #2838.
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
• github-review-approved [🛡 GitHub repository ruleset rule main]
  • Update dependency pytest-mergify to >=2026.9.18.1 #2838
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = @mergify/Mergify Merge Protections
  • check-skipped = @mergify/Mergify Merge Protections
  • check-success = @mergify/Mergify Merge Protections

Required conditions to stay in the queue:

• author = renovate[bot]
  • Update dependency pytest-mergify to >=2026.9.18.1 #2838
• check-success = Check Dependency Compatibility
  • Update dependency pytest-mergify to >=2026.9.18.1 #2838
• files ~= ^(uv.lock|pyproject.toml)$
  • Update dependency pytest-mergify to >=2026.9.18.1 #2838
• github-review-approved [🛡 GitHub repository ruleset rule main]
  • Update dependency pytest-mergify to >=2026.9.18.1 #2838
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = @mergify/Mergify Merge Protections
    • Update dependency pytest-mergify to >=2026.9.18.1 #2838
  • check-skipped = @mergify/Mergify Merge Protections
    • Update dependency pytest-mergify to >=2026.9.18.1 #2838
  • check-success = @mergify/Mergify Merge Protections
    • Update dependency pytest-mergify to >=2026.9.18.1 #2838

---
checking_base_sha: f33bbb082402653e7b12cc691783ef8cfe2990d9
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 2838
    scopes: []
scopes: []
...

[semanticdiff-com]

Review changes with  

[deepsource-io]

DeepSource Code Review

We reviewed changes in f33bbb0...4245a90 on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade

Security   Reliability   Complexity   Hygiene

Code Review Summary

Analyzer	Status	Updated (UTC)	Details
Shell		Aug 5, 2026 1:14p.m.	Review ↗
Python		Aug 5, 2026 1:14p.m.	Review ↗
Docker		Aug 5, 2026 1:14p.m.	Review ↗
Secrets		Aug 5, 2026 1:14p.m.	Review ↗

---

Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates the pytest-mergify development dependency version and refreshes the corresponding uv lockfile to align with the new requirement, as part of a Mergify-managed merge-queue check for Python dependency updates.

File-Level Changes

Change	Details	Files
Bump pytest-mergify dev dependency and regenerate lockfile to match.	Increase the pytest-mergify dev dependency version constraint from 2026.8.3.1 to 2026.8.5.1 in the pyproject configuration. Regenerate or update the uv.lock file so its resolved dependency graph is consistent with the new pytest-mergify version and any transitive updates.	pyproject.toml uv.lock

Possibly linked issues

• #: PR implements the pytest-mergify >=2026.8.5.1 update explicitly listed in the Renovate dashboard issue.

---

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.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	pytest-mergify@​2026.8.3.1 ⏵ 2026.8.5.1	+1

View full report

[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