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

[mergify]

✨ Pull request #344 which was ahead in the queue has been dequeued (for the following reason: pull request manually updated). The pull request #372 has been requeued. ✨

Branch main (0ea46b4), #348, #344, #370, #371 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 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 actions/cache digest to caa2961 #372
• 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: 503cdf9cbe2c64016b27a6647052b2e1fa77eb9a
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, generated by Mergify/renovate, updates CI workflows and project configuration by bumping GitHub Actions versions, tightening the Python version floor, and updating a dev dependency version, with no behavioral code changes to the application itself.

File-Level Changes

Change	Details	Files
Bump GitHub Actions used in workflows to newer pinned SHAs for github-script, upload-artifact, and cache to keep CI infrastructure up to date and secure.	Update multiple steps in the code-simplifier.lock workflow to use actions/github-script v9 instead of v8 by changing the pinned commit SHA Update artifact upload steps in the code-simplifier.lock workflow to use actions/upload-artifact v7.0.1 instead of v7.0.0 Update steps in the agentics-maintenance workflow to use actions/github-script v9 instead of v8 by changing the pinned commit SHA Update the deploy workflow cache step to a newer pinned SHA of actions/cache v5	.github/workflows/code-simplifier.lock.yml .github/workflows/agentics-maintenance.yml .github/workflows/deploy.yml
Adjust Python and dev dependency versions in project configuration to align with upstream tooling updates.	Increase the minimum supported Python version from 3.14.3 to 3.14.6 in pyproject configuration Bump the ruff dev dependency minimum version from 0.15.9 to 0.15.10 in pyproject configuration	pyproject.toml

Possibly linked issues

• #0: PR’s dependency updates (e.g., actions/cache digest, github-script v9, Python version) are explicitly tracked in the dependency dashboard issue.
• #aw: The issue reports Code Simplifier workflow failure; this PR updates that workflow’s actions and tooling to fix it.

---

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