merge queue: embarking main (139da33), #1953, #1954 and #1859 together

[mergify]

✨ Pull request #1953 which was ahead in the queue has been dequeued (for the following reason: pull request manually updated). The pull request #1859 has been re-embarked. ✨

Branch main (139da33), #1953, #1954 and #1859 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #1859.
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 Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections

Required conditions to stay in the queue:

• author = renovate[bot]
  • Update dependency agno to >=2.6.7 #1859
• check-success = Check Dependency Compatibility
• files ~= ^(uv.lock|pyproject.toml)$
• 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: c729601e77d38fa7aa806bd28c0838204bcff0b1
previous_failed_batches: []
pull_requests:
  - number: 1859
    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
pyproject.toml	Unsupported file format
uv.lock	Unsupported file format

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	agno@​2.6.6 ⏵ 2.6.7	+1

View full report

[sourcery-ai]

Reviewer's Guide

This PR is an automated merge-queue batch that primarily pins GitHub Actions to specific commit SHAs in various workflow lockfiles, updates the CodeQL upload-sarif action to v4.36.0, and bumps the agno Python dependency from >=2.6.6 to >=2.6.7 with corresponding uv.lock updates.

File-Level Changes

Change	Details	Files
Pin reusable GitHub Actions setup helper to a specific commit SHA across CI workflow lockfiles.	Replace version tag github/gh-aw-actions/setup@v0.74.8 with commit SHA efa55847f72aadb03490d955263ff911bf758700 while retaining the version comment Apply the same pinning change in all workflow lockfiles that run the "Setup Scripts" step so all jobs use the exact same immutable action revision	.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 security scanning GitHub Action to the latest CodeQL upload-sarif version in the daily malicious code scan workflow.	Change github/codeql-action/upload-sarif reference from commit 9e0d7b8d25671d64c341c19c0152d693099fb5ba (v4.35.5) to 7211b7c8077ea37d8641b6271f6a365a22a5fbfa (v4.36.0) Keep the version comment in sync with the new CodeQL action version	.github/workflows/daily-malicious-code-scan.lock.yml
Bump agno Python dependency and refresh lockfile for dependency update PR.	Increase agno[google,qdrant] lower bound from >=2.6.6 to >=2.6.7 in project dependencies Regenerate uv.lock to reflect the updated agno version and any transitive dependency changes	pyproject.toml uv.lock

Possibly linked issues

• #Dependency Dashboard: This PR is a batch of Renovate dependency updates that are explicitly tracked in the Dependency 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.