merge queue: checking main (0ea46b4), #348, #344, #370, #371, #373, #372, #342, #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, #342, #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: adf0b7e86d2080922bb8c9a4658f78719287a94c
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 GitHub workflows and development tooling to newer pinned action and tool versions, plus slightly tightens the supported Python patch range and dev dependencies, with no behavioral code changes beyond CI/tooling updates.

File-Level Changes

Change	Details	Files
Update GitHub Actions workflows to newer pinned action SHAs for gh-aw setup, github-script, cache, upload-artifact, and upload-pages-artifact.	Bump github/gh-aw/actions setup and setup-cli actions from v0.67.1 to v0.83.4 across all workflows that use them. Upgrade actions/github-script from v8 to v9 for all workflow steps invoking custom scripts. Update actions/upload-artifact and upload-pages-artifact to the latest v7.0.1 and v5 SHAs respectively, and actions/cache to the latest v5 SHA. Ensure all changes keep workflow logic, job definitions, and environments identical aside from the action versions.	.github/workflows/code-simplifier.lock.yml .github/workflows/agentics-maintenance.yml .github/workflows/deploy.yml
Refresh local tooling configuration to newer versions of uv/ruff pre-commit hooks and adjust Python/dev dependency constraints.	Bump uv-pre-commit hook version from 0.11.3 to 0.11.32 and ruff-pre-commit from v0.15.9 to v0.16.0 in the pre-commit configuration. Narrow the supported Python patch version range from ">=3.14.3,<3.15" to ">=3.14.6,<3.15" in pyproject.toml. Raise the minimum dev dependency version for ruff from 0.15.9 to 0.15.10 in pyproject.toml. Regenerate the uv.lock file to align with the updated tool and dependency constraints.	.pre-commit-config.yaml pyproject.toml uv.lock

---

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 failed

Failed conditions
C Security Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE