merge queue: checking main (4423ecc), #2848 and #2838 together

[mergify]

✨ The pull request #2838 has been manually updated. ✨

Branch main (4423ecc), #2848 and #2838 are queued together for merge.

This pull request has been created by Mergify to speculatively 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
• 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
• github-review-approved [🛡 GitHub repository ruleset rule main]
  • Update dependency pytest-mergify to >=2026.9.18.1 #2838

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
• files ~= ^(uv.lock|pyproject.toml)$
• 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

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

[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.4.1	+1

View full report

[deepsource-io]

DeepSource Code Review

We reviewed changes in 4423ecc...7a6cfed 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:53a.m.	Review ↗
Python		Aug 5, 2026 1:53a.m.	Review ↗
Docker		Aug 5, 2026 1:53a.m.	Review ↗
Secrets		Aug 5, 2026 1:53a.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

This PR updates GitHub gh-aw workflow/setup actions and the pytest-mergify development dependency, along with regenerating the Python dependency lockfile to align with those changes, as part of a speculative merge check by Mergify.

File-Level Changes

Change	Details	Files
Update gh-aw GitHub Actions to v0.85.0 across CI workflows	Bump github/gh-aw-actions/setup from pinned v0.84.3 SHA to v0.85.0 SHA in multiple workflow lockfiles Bump github/gh-aw-actions/setup and setup-cli from pinned v0.84.4 SHA to v0.85.0 SHA in non-lock workflows Ensure all jobs using gh-aw setup scripts or CLI now share the same v0.85.0 action version	.github/workflows/ci-doctor.lock.yml .github/workflows/agents-md-maintenance.lock.yml .github/workflows/code-simplifier.lock.yml .github/workflows/ci-coach.lock.yml .github/workflows/daily-malicious-code-scan.lock.yml .github/workflows/agentics-maintenance.yml .github/workflows/ci_tools.yaml
Update pytest-mergify development dependency and regenerate lockfile	Increase pytest-mergify dev dependency minimum version from 2026.8.3.1 to 2026.8.4.1 Regenerate uv.lock to capture updated dependency graph for pytest-mergify and any transitive changes	pyproject.toml uv.lock

---

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