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

[mergify]

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

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

This pull request has been created by Mergify to speculatively check the mergeability of #349.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule pre-commit 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 pre-commit hook astral-sh/ruff-pre-commit to v0.16.3 #349
• files ~= .pre-commit-config.yaml
  • chore(deps): update pre-commit hook astral-sh/ruff-pre-commit to v0.16.3 #349
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = @mergify/Mergify Merge Protections
    • chore(deps): update pre-commit hook astral-sh/ruff-pre-commit to v0.16.3 #349
  • check-skipped = @mergify/Mergify Merge Protections
    • chore(deps): update pre-commit hook astral-sh/ruff-pre-commit to v0.16.3 #349
  • check-success = @mergify/Mergify Merge Protections
    • chore(deps): update pre-commit hook astral-sh/ruff-pre-commit to v0.16.3 #349

---
checking_base_sha: 5224b4b771015def817a85c66031b5c9fac0f33b
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 349
    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 updates GitHub Actions workflows and Python tooling constraints to newer, pinned versions for the agentic workflows, deployment pipeline, and development tooling, largely as part of an automated maintenance/merge-queue batch.

Flow diagram for updated deploy workflow CI pipeline

flowchart LR
  trigger["Push_to_main_or_release"] --> gha["GitHub_Actions_runner"]
  gha --> checkout["actions/checkout@v6"]
  checkout --> cache["actions/cache@v5"]
  cache --> deps["uv_sync_dependencies"]
  deps --> build["uv_run_reflex_export"]
  build --> upload["actions/upload-pages-artifact@v5"]
  upload --> pages["GitHub_Pages_deploy"]

Loading

File-Level Changes

Change	Details	Files
Bump versions of reusable GitHub Actions used by the agentic workflows and maintenance jobs to newer pinned SHAs.	Update github/gh-aw/actions setup and setup-cli actions to v0.81.6 across code-simplifier and agentics-maintenance workflows. Upgrade multiple uses of actions/github-script from v8 to v9 in code-simplifier and agentics-maintenance workflows, including steps that generate metadata, manage PR state, process agent outputs, and enforce permissions. Bump actions/upload-artifact from v7.0.0 to v7.0.1 for activation, agent, threat-detection, and safe-output artifacts. Update actions/cache and actions/upload-pages-artifact to newer v5 SHAs in the deploy workflow.	.github/workflows/code-simplifier.lock.yml .github/workflows/agentics-maintenance.yml .github/workflows/deploy.yml
Refresh Python tooling constraints to newer compatible versions.	Increase the minimum supported Python patch version from 3.14.3 to 3.14.6 in pyproject configuration. Bump the development dependency ruff from >=0.15.9 to >=0.15.10 in pyproject. Align pre-commit ruff hook to ruff-pre-commit v0.15.21 to match newer ruff tooling.	pyproject.toml .pre-commit-config.yaml uv.lock

Possibly linked issues

• #aw: The PR updates .github/workflows/code-simplifier.lock.yml, directly modifying the failing Code Simplifier workflow from the 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.

[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