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

[mergify]

✨ Pull request #349 which was ahead in the queue has been dequeued (for the following reason: pull request manually updated). The pull request [#370 + #371 + #372 + #373 + #369] has been re-embarked. ✨

Branch main (a4ccdc8), #348, #349, #337, #344 and [#370 + #371 + #372 + #373 + #369] are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of [#370 + #371 + #372 + #373 + #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.73.0 #369
  • chore(deps): update actions/github-script action to v9 #370
  • chore(deps): update actions/upload-artifact action to v7.0.1 #371
  • chore(deps): update actions/cache digest to 27d5ce7 #372
  • chore(deps): update actions/upload-pages-artifact action to v5 #373
• files ~= ^.github/workflows
• 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: 312d104de0019661bd6fe91d4c8013108a77dfd7
previous_failed_batches: []
pull_requests:
  - number: 370
    scopes: []
  - number: 371
    scopes: []
  - number: 372
    scopes: []
  - number: 373
    scopes: []
  - number: 369
    scopes: []
scopes: []
...

[sourcery-ai]

Reviewer's Guide

Update GitHub Actions workflows and development tooling versions, including GitHub composite actions, cache/artifact actions, Python requirement, and Ruff linter, with corresponding lockfile refresh.

Flow diagram for updated deploy workflow

flowchart TD
  TRIGGER[push to main or configured branches] --> START[Start deploy workflow]

  START --> JOB_build[Job deploy_build]

  subgraph deploy_build_steps[Job deploy_build steps]
    B1[Checkout repository using actions/checkout v6]
    B2[Restore and save .web cache using actions/cache v5]
    B3[Install dependencies with uv]
    B4[Build static site with uv run reflex export]
    B5[Upload build artifact using actions/upload-pages-artifact v5]
  end

  JOB_build --> B1 --> B2 --> B3 --> B4 --> B5

  B5 --> JOB_deploy_web[Job deploy_web]

  subgraph deploy_web_steps[Job deploy_web steps]
    W1[Download artifact]
    W2[Deploy to GitHub Pages]
  end

  JOB_deploy_web --> W1 --> W2 --> END[Deployment complete]

Loading

File-Level Changes

Change	Details	Files
Bump gh-aw setup actions and actions/github-script versions across automation workflows.	Update github/gh-aw/actions/setup to v0.68.3 in all relevant jobs. Upgrade actions/github-script from v8 to v9 for all workflow steps that run Node-based scripts. Update github/gh-aw/actions/setup-cli to v0.68.3 in maintenance workflows.	.github/workflows/code-simplifier.lock.yml .github/workflows/agentics-maintenance.yml
Update cache and artifact-related GitHub Actions used in deployment and automation workflows.	Bump actions/cache from v5 (old SHA) to newer v5 commit for .web caching. Bump actions/upload-pages-artifact from v4 to v5 for deploying built frontend artifacts. Bump actions/upload-artifact from v7.0.0 to v7.0.1 everywhere it is used.	.github/workflows/code-simplifier.lock.yml .github/workflows/deploy.yml
Tighten Python version floor and refresh dev tooling versions and lockfiles.	Increase requires-python minimum from 3.14.3 to 3.14.4 in pyproject.toml. Bump Ruff dev dependency from >=0.15.9 to >=0.15.10. Align pre-commit ruff-pre-commit hook rev to v0.15.10. Regenerate uv.lock to reflect updated Python/tooling constraints.	pyproject.toml .pre-commit-config.yaml uv.lock

Possibly linked issues

• #0: The merge-queue PR merges the Renovate dependency and GitHub Actions update PRs tracked by the Dependency Dashboard.

---

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