Skip to content

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

Draft
mergify[bot] wants to merge 13 commits into
mainfrom
mergify/merge-queue/66fb69372a
Draft

merge queue: checking main (0ea46b4), #348, #370, #371, #373, #372 and #349 together#476
mergify[bot] wants to merge 13 commits into
mainfrom
mergify/merge-queue/66fb69372a

Conversation

@mergify

@mergify mergify Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

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

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

This pull request has been created by Mergify to speculatively check the mergeability of #349.
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:

---
checking_base_sha: 7f0716f8790241197ec7de600efba649c91d2af7
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 349
    scopes: []
scopes: []
...

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedruff@​0.15.9 ⏵ 0.15.10100100100100100

View full report

@sourcery-ai

sourcery-ai Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Reviewer's Guide

This PR updates GitHub Actions workflow dependencies and Python tooling versions (ruff and related lockfile) to newer, pinned revisions, ensuring CI and pre-commit hooks use the latest vetted versions.

Flow diagram for updated CI and tooling versions

flowchart LR
    dev[Developer changes code]
    precommit[pre-commit: ruff-pre-commit v0.16.1]
    gitpush[Push to GitHub]
    ci[GitHub Actions workflows]
    deploy[Deploy workflow: cache v5, upload-pages-artifact v5]
    artifacts[Code Simplifier artifacts: upload-artifact v7.0.1]
    scripts[Workflow scripts: actions/github-script v9]

    dev --> precommit --> gitpush --> ci
    ci --> scripts
    ci --> deploy
    ci --> artifacts
Loading

File-Level Changes

Change Details Files
Bump GitHub Actions workflow actions to newer pinned SHAs for github-script, upload-artifact, cache, and upload-pages-artifact.
  • Update all uses of actions/github-script from v8 SHA to v9 SHA in the code-simplifier.lock workflow, including steps for workflow timestamp checks, prompt interpolation/substitution, PR handling, logging, threat detection, and various post-processing handlers.
  • Update all uses of actions/upload-artifact from v7.0.0 SHA to v7.0.1 SHA in the code-simplifier.lock workflow for activation, agent artifacts, threat detection logs, and safe output manifests.
  • Update actions/cache in the deploy workflow to a newer v5 SHA for caching the .web directory.
  • Update actions/upload-pages-artifact in the deploy workflow from v4 SHA to v5 SHA for publishing the built site artifacts.
  • Update actions/github-script usages in the agentics-maintenance workflow (closing expired items, permission checks, and running operations) from v8 SHA to v9 SHA.
.github/workflows/code-simplifier.lock.yml
.github/workflows/deploy.yml
.github/workflows/agentics-maintenance.yml
Update ruff tooling versions and lockfile to align with newer releases.
  • Bump the ruff-pre-commit hook revision in .pre-commit-config.yaml from v0.15.9 to v0.16.1.
  • Increase the dev dependency constraint for ruff in pyproject.toml from >=0.15.9 to >=0.15.10.
  • Regenerate or update uv.lock to reflect the new ruff and tooling versions.
.pre-commit-config.yaml
pyproject.toml
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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants