merge queue: checking main (0ea46b4), #348, #344, #370, #371, #373, #372, #349 and #369 together

[mergify]

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (0ea46b4), #348, #344, #370, #371, #373, #372, #349 and #369 are queued together for merge.

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

Required conditions to stay in the queue:

• author = renovate[bot]
  • chore(deps): update github/gh-aw action to v0.86.2 #369
• files ~= ^.github/workflows
  • chore(deps): update github/gh-aw action to v0.86.2 #369
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = @mergify/Mergify Merge Protections
    • chore(deps): update github/gh-aw action to v0.86.2 #369
  • check-skipped = @mergify/Mergify Merge Protections
    • chore(deps): update github/gh-aw action to v0.86.2 #369
  • check-success = @mergify/Mergify Merge Protections
    • chore(deps): update github/gh-aw action to v0.86.2 #369

---
checking_base_sha: 073ff7561f603b399d79aa046e8948d4d231b9d1
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 369
    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
	ruff@​0.15.9 ⏵ 0.15.10

View full report

[sourcery-ai]

Reviewer's Guide

This PR refreshes CI tooling by bumping pinned GitHub Actions, cache/artifact/upload actions, development tooling versions, and Python constraints, keeping workflows and tooling aligned with newer upstream releases while preserving behavior.

File-Level Changes

Change	Details	Files
Update GitHub Actions workflows to use newer pinned versions of gh-aw, actions/github-script, cache, upload-artifact, upload-pages-artifact, and related actions.	Bump github/gh-aw/actions setup and setup-cli pins from v0.67.1 to v0.84.3 across all affected workflows. Upgrade actions/github-script from v8 to v9 everywhere it is used in CI and maintenance workflows. Update actions/cache, actions/upload-artifact, and actions/upload-pages-artifact pins to their latest v5/v7 patch SHAs while keeping configurations unchanged.	.github/workflows/code-simplifier.lock.yml .github/workflows/agentics-maintenance.yml .github/workflows/deploy.yml
Refresh Python and linting tooling constraints to newer compatible versions.	Raise the minimum supported Python patch version from 3.14.3 to 3.14.6 within the existing <3.15 range. Update the dev dependency on ruff from >=0.15.9 to >=0.15.10 and align the pre-commit ruff hook rev from v0.15.9 to v0.16.1. Regenerate or adjust the uv.lock file to match the updated dependency versions.	pyproject.toml .pre-commit-config.yaml uv.lock

Possibly linked issues

• #Dependency Dashboard: The PR’s GitHub Actions, Python, and ruff-related updates correspond exactly to items listed in the Dependency Dashboard.
• #0: PR upgrades gh-aw setup, github-script, and related actions in code-simplifier workflow, directly addressing the failure 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.