merge queue: embarking main (ebe3f51), #1891 and #1923 together

[mergify]

✨ Pull request #1891 which was ahead in the queue has been dequeued (for the following reason: checks failed). The pull request #1923 has been re-embarked. ✨

Branch main (ebe3f51), #1891 and #1923 are embarked together for merge.

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

Required conditions of queue rule Github Actions Updates for merge:

• 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 github/gh-aw-actions action to v0.74.9 #1923
• any of:
  • files ~= ^.github/workflows
    • Update github/gh-aw-actions action to v0.74.9 #1923
  • files ~= action.yaml$
    • Update github/gh-aw-actions action to v0.74.9 #1923
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
    • Update github/gh-aw-actions action to v0.74.9 #1923
  • check-skipped = Mergify Merge Protections
    • Update github/gh-aw-actions action to v0.74.9 #1923
  • check-success = Mergify Merge Protections
    • Update github/gh-aw-actions action to v0.74.9 #1923

---
checking_base_sha: 4fb6f2fc45c3d9908deb660805b3d5d4f7acb29c
previous_failed_batches: []
pull_requests:
  - number: 1923
    scopes: []
scopes: []
...

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
.github/workflows/agentics-maintenance.yml	19% smaller
.github/workflows/ci_tools.yaml	18% smaller
.github/workflows/daily-malicious-code-scan.lock.yml	18% smaller
.github/workflows/agents-md-maintenance.lock.yml	18% smaller
.github/workflows/ci-coach.lock.yml	18% smaller
.github/workflows/code-simplifier.lock.yml	18% smaller
.github/workflows/ci-doctor.lock.yml	18% smaller
pyproject.toml	Unsupported file format
uv.lock	Unsupported file format

[sourcery-ai]

Reviewer's Guide

Bumps GitHub gh-aw setup actions and uv-build dev dependency versions across CI workflows and lockfiles to align with newer tooling releases, as part of a Mergify merge-queue batch.

File-Level Changes

Change	Details	Files
Update GitHub gh-aw setup Actions to v0.74.9 across CI workflows.	Bump github/gh-aw-actions/setup from commit efa5584 (v0.74.8) to 318d7f4 (v0.74.9) in multiple locked workflow files. Bump github/gh-aw-actions/setup-cli from commit efa5584 (v0.74.8) to 318d7f4 (v0.74.9) in maintenance and CI tooling workflows. Keep workflow job structures and inputs identical while only changing action SHAs/comments.	.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
Align Python tooling dependency uv-build to a newer patch release and regenerate lockfile.	Increase dev dependency constraint uv-build from >=0.11.14 to >=0.11.15 in pyproject.toml. Regenerate uv.lock to reflect the updated uv-build version and transitive dependency resolution.	pyproject.toml uv.lock

Possibly linked issues

• #unknown: PR bumps gh-aw setup in agents-md-maintenance workflows, likely fixing the AGENTS.md Maintenance workflow failure.

---

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