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

[mergify]

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

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

This pull request has been created by Mergify to speculatively check the mergeability of #342.
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/uv-pre-commit to v0.12.5 #342
• files ~= .pre-commit-config.yaml
  • chore(deps): update pre-commit hook astral-sh/uv-pre-commit to v0.12.5 #342
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = @mergify/Mergify Merge Protections
    • chore(deps): update pre-commit hook astral-sh/uv-pre-commit to v0.12.5 #342
  • check-skipped = @mergify/Mergify Merge Protections
    • chore(deps): update pre-commit hook astral-sh/uv-pre-commit to v0.12.5 #342
  • check-success = @mergify/Mergify Merge Protections
    • chore(deps): update pre-commit hook astral-sh/uv-pre-commit to v0.12.5 #342

---
checking_base_sha: 7e4fc8a5847fbcdae3993cce0d1d4560971433ca
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 342
    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 merge-queue check that primarily bumps GitHub Actions, pre-commit hooks, Python/tooling versions, and refreshes the uv lockfile to align with the updated tooling stack.

File-Level Changes

Change	Details	Files
Update GitHub Actions versions for scripting, artifact handling, caching, and Pages deployment in CI workflows.	Bump actions/github-script from v8 to v9 across the code-simplifier and agentics-maintenance workflows. Upgrade actions/upload-artifact from v7.0.0 to v7.0.1 in multiple artifact-upload steps. Update actions/cache to a newer v5 commit in the deploy workflow. Upgrade actions/upload-pages-artifact from v4 to v5 in the deploy workflow.	.github/workflows/code-simplifier.lock.yml .github/workflows/agentics-maintenance.yml .github/workflows/deploy.yml
Refresh pre-commit tooling versions for uv and ruff hooks.	Bump uv-pre-commit hook revision from 0.11.3 to 0.12.2. Bump ruff-pre-commit hook revision from v0.15.9 to v0.16.1.	.pre-commit-config.yaml
Align Python and development dependency versions with the updated toolchain.	Raise requires-python from >=3.14.3,<3.15 to >=3.14.6,<3.15. Increase dev dependency lower bound for ruff from 0.15.9 to 0.15.10.	pyproject.toml
Regenerate the uv lockfile to reflect the updated tooling and dependency versions.	Update locked dependency metadata and versions in uv.lock to stay consistent with pyproject and pre-commit changes.	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.