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

[mergify]

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

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

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

---
checking_base_sha: 7e28e3e2f690a0c5b56a1bb8046b56baf8aed5cf
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 371
    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 workflow dependencies and Python dev tooling versions to their latest pinned revisions, ensuring CI maintenance and compatibility across the code-simplifier and agentics-maintenance workflows as part of a merge-queue check for #371.

File-Level Changes

Change	Details	Files
Update GitHub Actions workflow steps to use newer pinned versions of actions/github-script and actions/upload-artifact.	Bump actions/github-script from v8 to v9 across multiple steps in the code-simplifier.lock workflow, keeping scripts and env usage unchanged. Update actions/upload-artifact from v7.0.0 to v7.0.1 for artifact upload steps in the code-simplifier.lock workflow, preserving artifact names and paths.	.github/workflows/code-simplifier.lock.yml
Refresh automation in the agentics-maintenance workflow to use the newer github-script action revision.	Bump actions/github-script from v8 to v9 in maintenance jobs that close expired discussions, issues, and pull requests. Update github-script usage for permission checking and running operations while preserving existing scripts and inputs.	.github/workflows/agentics-maintenance.yml
Update Python dev dependency version and associated lockfile entries.	Increase the minimum ruff dev dependency from 0.15.9 to 0.15.10 in pyproject.toml while keeping other constraints the same. Regenerate or adjust uv.lock to align with the new dependency versions and ensure consistent environment locking.	pyproject.toml uv.lock

Possibly linked issues

• #unknown: PR upgrades actions in code-simplifier.lock.yml, directly changing the workflow that failed 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.