merge queue: embarking main (139da33) and [#1953 + #1954] together

[mergify]

✨ The pull request #1953 has been manually updated. The pull request #1954 has been re-embarked. ✨

Branch main (139da33) and [#1953 + #1954] are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of [#1953 + #1954].
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:

• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections
• author = renovate[bot]
  • Pin github/gh-aw-actions action to efa5584 - autoclosed #1953
  • Update github/codeql-action action to v4.36.0 #1954
• any of:
  • files ~= ^.github/workflows
  • files ~= action.yaml$

---
checking_base_sha: 139da3326e8f8d5f399b216177e044ff90aa479d
previous_failed_batches: []
pull_requests:
  - number: 1953
    scopes: []
  - number: 1954
    scopes: []
scopes: []
...

[semanticdiff-com]

Review changes with  

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

[sourcery-ai]

Reviewer's Guide

Pins GitHub Actions workflows to a specific commit SHA for the gh-aw setup action and bumps the CodeQL upload-sarif action to v4.36.0 in several locked workflow files.

Flow diagram for updated GitHub Actions workflow pinning and CodeQL upload

flowchart LR
    Wf["GitHub Actions workflow run"] --> Setup["github/gh-aw-actions/setup@efa55847f72aadb03490d955263ff911bf758700"]
    Setup --> BuildAndScan["Build and scan jobs"]
    BuildAndScan --> Upload["github/codeql-action/upload-sarif@7211b7c8077ea37d8641b6271f6a365a22a5fbfa (v4.36.0)"]
    Upload --> CodeScanning["GitHub Code Scanning alerts"]

Loading

File-Level Changes

Change	Details	Files
Pin the gh-aw setup GitHub Action to a specific commit SHA across multiple locked CI workflows.	Replace version-tagged reference to github/gh-aw-actions/setup@v0.74.8 with a commit-SHA-pinned reference while preserving the version comment. Apply this change consistently in all jobs that run the "Setup Scripts" step within the affected workflow lockfiles.	.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 CodeQL SARIF upload action to a newer version in the daily malicious code scan workflow lockfile.	Change github/codeql-action/upload-sarif from v4.35.5 to v4.36.0 via a new commit SHA. Keep existing step configuration (token and sarif_file inputs) unchanged.	.github/workflows/daily-malicious-code-scan.lock.yml

Possibly linked issues

• #: PR fulfills dashboard’s open items to pin github/gh-aw-actions and update github/codeql-action to v4.36.0.

---

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