merge queue: checking main (0ea46b4), #348, #344, #370, #371, #373, #372, #349, #369 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, #369 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: 2c388e593c5208a3e4e2320a886615bc4b8fc674
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 updates GitHub Actions workflows, pre-commit hooks, and Python tooling constraints to newer pinned versions, ensuring CI, deployment, and code-quality tooling stay in sync with upstream while keeping behavior functionally equivalent.

Flow diagram for updated CI and tooling pipeline

flowchart TD
  A[Push or pull_request event] --> B[code-simplifier workflow
uses github/gh-aw/actions/setup v0.84.3]
  B --> C[actions/github-script v9
for agentic steps]

  A --> D[deploy workflow]
  D --> E[actions/cache v5
updated commit]
  E --> F[actions/upload-pages-artifact v5
for static site]

  A --> G[Pre-commit and tooling]
  G --> H[uv-pre-commit rev 0.12.2
uv-sync, uv-lock]
  G --> I[ruff-pre-commit v0.16.1
ruff-check]
  G --> J[pyproject updates
requires-python >=3.14.6
ruff dev >=0.15.10]

Loading

File-Level Changes

Change	Details	Files
Refresh Code Simplifier workflow to newer gh-aw, actions/github-script, and upload-artifact versions.	Bump github/gh-aw/actions/setup from v0.67.1 to v0.84.3 across all Code Simplifier jobs. Upgrade actions/github-script uses from v8 to v9 for workflow info generation, PR checkout, lockdown determination, log parsing, threat detection, safe-output processing, and error/no-op handling. Update actions/upload-artifact from v7.0.0 to v7.0.1 for activation, agent, detection, and safe-output manifests. Keep workflow logic and environment variables unchanged while only refreshing action SHAs.	.github/workflows/code-simplifier.lock.yml
Update agentics maintenance workflow dependencies to newer gh-aw and github-script versions.	Upgrade github/gh-aw/actions/setup from v0.67.1 to v0.84.3 for maintenance jobs. Upgrade github/gh-aw/actions/setup-cli from v0.67.1 to v0.84.3. Bump actions/github-script from v8 to v9 for closing expired items, permission checks, and running maintenance operations.	.github/workflows/agentics-maintenance.yml
Refresh deploy workflow cache and artifact upload actions to latest v5/v4 SHAs.	Update actions/cache v5 to a newer pinned SHA for caching .web artifacts. Upgrade actions/upload-pages-artifact from v4 to v5 for publishing the built site.	.github/workflows/deploy.yml
Update pre-commit hooks and dev tooling versions for uv and ruff.	Bump uv-pre-commit hook rev from 0.11.3 to 0.12.2 while keeping hook IDs and args the same. Bump ruff-pre-commit hook rev from v0.15.9 to v0.16.1. Update dev dependency constraint ruff>=0.15.9 to ruff>=0.15.10 in pyproject.toml.	.pre-commit-config.yaml pyproject.toml
Tighten minimum supported Python version in project metadata.	Increase requires-python lower bound from >=3.14.3 to >=3.14.6, keeping the <3.15 upper bound unchanged.	pyproject.toml
Regenerate uv.lock to align with updated tooling and constraints.	Refresh uv.lock to reflect new dependency and tooling versions implied by updated pre-commit hooks and Python constraints.	uv.lock

Possibly linked issues

• #Dependency Dashboard: This PR updates actions, pre-commit hooks, and Python dependencies exactly as enumerated in the Dependency Dashboard.
• #0: The PR upgrades gh-aw setup, github-script, and artifacts in code-simplifier.lock.yml to fix the failing workflow.

---

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.