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

[mergify]

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

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

This pull request has been created by Mergify to speculatively check the mergeability of #372.
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 actions/cache digest to caa2961 #372
• files ~= ^.github/workflows
  • chore(deps): update actions/cache digest to caa2961 #372
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = @mergify/Mergify Merge Protections
    • chore(deps): update actions/cache digest to caa2961 #372
  • check-skipped = @mergify/Mergify Merge Protections
    • chore(deps): update actions/cache digest to caa2961 #372
  • check-success = @mergify/Mergify Merge Protections
    • chore(deps): update actions/cache digest to caa2961 #372

---
checking_base_sha: 37a4e9ad1ede51a6bcefe8edc9e4eb0a26bce326
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 372
    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 is an automated Renovate/Mergify update that bumps various GitHub Actions and Python tooling versions, updating workflow references, project metadata, and the lockfile to their new pinned revisions without changing application logic.

File-Level Changes

Change	Details	Files
Update GitHub Actions workflow steps to newer pinned versions of actions/github-script, actions/upload-artifact, actions/cache, and actions/upload-pages-artifact.	Bump actions/github-script from v8 SHA to v9 SHA across the code-simplifier.lock workflow for all steps that invoke custom Node scripts. Bump actions/upload-artifact from v7.0.0 to v7.0.1 in the code-simplifier.lock workflow for activation, agent, detection, and safe-output-items artifacts. Bump actions/github-script from v8 SHA to v9 SHA throughout the agentics-maintenance workflow for maintenance/cleanup operations. Bump actions/cache to a newer v5 SHA for caching the .web directory in the deploy workflow. Bump actions/upload-pages-artifact from v4 to v5 in the deploy workflow for publishing the built frontend.	.github/workflows/code-simplifier.lock.yml .github/workflows/agentics-maintenance.yml .github/workflows/deploy.yml
Refresh Python project/tooling constraints (runtime requirement and linting tooling) and corresponding lockfile.	Increase the minimum required Python patch version from 3.14.3 to 3.14.6 in pyproject.toml. Bump the ruff development dependency lower bound from 0.15.9 to 0.15.10 in pyproject.toml. Update the ruff pre-commit hook revision from v0.15.9 to v0.15.20 in .pre-commit-config.yaml. Regenerate or adjust uv.lock to align with the updated dependency/tooling constraints.	pyproject.toml .pre-commit-config.yaml 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 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