Skip to content

merge queue: embarking main (f751d66), #1903, #1891 and #1904 together#1908

Closed
mergify[bot] wants to merge 7 commits into
mainfrom
mergify/merge-queue/ea19c69cdc
Closed

merge queue: embarking main (f751d66), #1903, #1891 and #1904 together#1908
mergify[bot] wants to merge 7 commits into
mainfrom
mergify/merge-queue/ea19c69cdc

Conversation

@mergify

@mergify mergify Bot commented May 20, 2026

Copy link
Copy Markdown
Contributor

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

Branch main (f751d66), #1903, #1891 and #1904 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #1904.
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]
  • any of:
    • files ~= ^.github/workflows
    • files ~= action.yaml$
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections
---
checking_base_sha: 9373618c0c61df87eb24cd1b5b794c942c9441aa
previous_failed_batches: []
pull_requests:
  - number: 1904
    scopes: []
scopes: []
...

@semanticdiff-com

semanticdiff-com Bot commented May 20, 2026

Copy link
Copy Markdown

Review changes with  SemanticDiff

Changed Files
File Status
  .github/workflows/agents-md-maintenance.lock.yml  0% smaller
  .github/workflows/ci-coach.lock.yml  0% smaller
  .github/workflows/ci-doctor.lock.yml  0% smaller
  .github/workflows/code-simplifier.lock.yml  0% smaller
  .github/workflows/daily-malicious-code-scan.lock.yml  0% smaller
  pyproject.toml Unsupported file format
  uv.lock Unsupported file format

@sourcery-ai

sourcery-ai Bot commented May 20, 2026

Copy link
Copy Markdown
Contributor

Reviewer's Guide

This PR updates GitHub Actions workflow lockfiles to pin the gh-aw setup action to a specific commit, bumps the CodeQL upload-sarif action patch version, and increments the uv-build development dependency along with its lockfile.

File-Level Changes

Change Details Files
Pin the gh-aw setup GitHub Action to a specific commit hash across CI-related workflow lockfiles.
  • Replace version tag v0.74.4 of github/gh-aw-actions/setup with commit d3abfe96a194bce3a523ed2093ddedd5704cdf62 in all jobs using this action
  • Preserve the original version as an inline comment for reference
.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
Update GitHub CodeQL upload-sarif action to the latest patch version in the daily malicious code scan workflow.
  • Bump github/codeql-action/upload-sarif from commit 68bde559dea0fdcac2102bfdf6230c5f70eb485e (v4.35.4) to 9e0d7b8d25671d64c341c19c0152d693099fb5ba (v4.35.5)
.github/workflows/daily-malicious-code-scan.lock.yml
Bump uv-build dev dependency and refresh uv lockfile.
  • Increase uv-build minimum version from 0.11.14 to 0.11.15 in dev dependencies
  • Regenerate uv.lock to reflect updated dependency resolution
pyproject.toml
uv.lock

Possibly linked issues

  • #: PR bumps the github/gh-aw-actions/setup reference in agents-md-maintenance.lock.yml, likely fixing the reported AGENTS.md Maintenance 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

@sonarqubecloud

Copy link
Copy Markdown

@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:37 Failure
@mergify mergify Bot temporarily deployed to code_quality May 20, 2026 02:37 Inactive
@mergify mergify Bot temporarily deployed to code_quality May 20, 2026 02:37 Inactive
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:37 Failure
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:37 Failure
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:37 Failure
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:37 Failure
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:37 Failure
@mergify mergify Bot temporarily deployed to code_quality May 20, 2026 02:37 Inactive
@mergify mergify Bot temporarily deployed to code_quality May 20, 2026 02:37 Inactive
@mergify mergify Bot temporarily deployed to code_quality May 20, 2026 02:37 Inactive
@mergify mergify Bot temporarily deployed to code_quality May 20, 2026 02:37 Inactive
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:37 Failure
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:37 Failure
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:37 Failure
@mergify mergify Bot temporarily deployed to code_quality May 20, 2026 02:37 Inactive
@mergify mergify Bot temporarily deployed to code_quality May 20, 2026 02:37 Inactive
@mergify mergify Bot temporarily deployed to code_quality May 20, 2026 02:37 Inactive
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:37 Failure
@mergify mergify Bot temporarily deployed to code_quality May 20, 2026 02:37 Inactive
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:37 Failure
@mergify mergify Bot had a problem deploying to docker_image May 20, 2026 02:37 Failure
@mergify mergify Bot closed this May 20, 2026
@mergify mergify Bot deleted the mergify/merge-queue/ea19c69cdc branch May 20, 2026 02:38
@mergify mergify Bot temporarily deployed to docker_image May 20, 2026 02:39 Inactive
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:41 Failure
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:41 Failure
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:41 Failure
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:41 Failure
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:41 Failure
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:41 Failure
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:41 Failure
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:41 Failure
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:41 Failure
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:41 Failure
@mergify mergify Bot had a problem deploying to code_quality May 20, 2026 02:41 Failure
@mergify mergify Bot had a problem deploying to docker_image May 20, 2026 02:41 Failure
@mergify mergify Bot temporarily deployed to docker_image May 20, 2026 02:42 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants