merge queue: embarking main (a4ccdc8), #348, #337, #344, #370, #371, #372, #373, #349, #342 and #369 together

[mergify]

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

Branch main (a4ccdc8), #348, #337, #344, #370, #371, #372, #373, #349, #342 and #369 are embarked 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 Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections

Required conditions to stay in the queue:

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

---
checking_base_sha: fca7e4fc1576eed7a45d4144e280f8fe2747dd01
previous_failed_batches: []
pull_requests:
  - number: 369
    scopes: []
scopes: []
...

[sourcery-ai]

Reviewer's Guide

Refreshes CI tooling and workflows by bumping GitHub Actions, pre-commit hooks, and Python/ruff versions, plus regenerating the uv.lock to align with the updated toolchain.

Flow diagram for updated deploy workflow using new cache and upload-pages-artifact actions

flowchart TD
  trigger["Push to main or configured branch"] --> job_build_web

  subgraph Job_build_web
    job_build_web["Job build_web"]
    job_build_web --> step_checkout
    step_checkout["Checkout repository using actions/checkout@v6"] --> step_cache_web
    step_cache_web["Cache .web using actions/cache v5 (updated)"] --> step_setup_python
    step_setup_python["Set up Python and dependencies (uv)"] --> step_build
    step_build["Build site with uv run reflex export"] --> step_upload_artifact
    step_upload_artifact["Upload static site using actions/upload-pages-artifact v5 (updated)"] --> artifact_pages
    artifact_pages["Pages build artifact"]
  end

  artifact_pages --> job_deploy_web

  subgraph Job_deploy_web
    job_deploy_web["Job deploy_web"]
    job_deploy_web --> step_deploy_pages
    step_deploy_pages["Deploy to GitHub Pages"]
  end

Loading

File-Level Changes

Change	Details	Files
Update GitHub Actions workflows to newer action versions for code simplification, maintenance, deployment, and artifact handling.	Bump github/gh-aw/actions setup and setup-cli actions from v0.67.1 to v0.71.1 across code-simplifier and agentics-maintenance workflows. Upgrade actions/github-script from v8 to v9 everywhere it is used in the workflows. Upgrade actions/upload-artifact and actions/upload-pages-artifact to their latest v7/v5 patch versions. Update actions/cache to a newer v5 commit for caching build artifacts.	.github/workflows/code-simplifier.lock.yml .github/workflows/agentics-maintenance.yml .github/workflows/deploy.yml
Refresh local development and packaging tooling versions (pre-commit hooks, Python requirement, and ruff dev dependency), and regenerate the lockfile accordingly.	Bump uv-pre-commit hook revision from 0.11.3 to 0.11.8 and ruff-pre-commit from v0.15.9 to v0.15.12. Raise the minimum supported Python version from 3.14.3 to 3.14.4 in pyproject configuration. Increase the ruff dev dependency floor from 0.15.9 to 0.15.10. Regenerate uv.lock to reflect the updated Python and tool versions.	.pre-commit-config.yaml pyproject.toml uv.lock

Possibly linked issues

• #0: The PR bumps Code Simplifier workflow actions and setup versions, directly addressing the workflow failure described in 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