Skip to content

ci: pre-commit auto-update#306

Open
pre-commit-ci[bot] wants to merge 1 commit into
masterfrom
pre-commit-ci-update-config
Open

ci: pre-commit auto-update#306
pre-commit-ci[bot] wants to merge 1 commit into
masterfrom
pre-commit-ci-update-config

Conversation

@pre-commit-ci

@pre-commit-ci pre-commit-ci Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

updates:

Summary by Sourcery

Update pre-commit hook versions for linting and packaging checks.

Build:

  • Bump ruff-pre-commit hook from v0.15.21 to v0.15.22 in .pre-commit-config.yaml.
  • Upgrade pyroma pre-commit hook from 5.0.1 to 5.1b1 in .pre-commit-config.yaml.

updates:
- [github.com/astral-sh/ruff-pre-commit: v0.15.21 → v0.15.22](astral-sh/ruff-pre-commit@v0.15.21...v0.15.22)
- [github.com/regebro/pyroma: 5.0.1 → 5.1b1](regebro/pyroma@5.0.1...5.1b1)
@sourcery-ai

sourcery-ai Bot commented Jul 20, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates pinned versions of two pre-commit hooks (ruff and pyroma) in the shared pre-commit configuration, keeping CI linting and packaging checks aligned with their latest releases.

File-Level Changes

Change Details Files
Update ruff-pre-commit hook to the latest tagged version in the pre-commit configuration.
  • Bump ruff-pre-commit revision from v0.15.21 to v0.15.22 in the pre-commit config
  • Keep existing ruff-check and ruff-format hooks configuration unchanged
.pre-commit-config.yaml
Update pyroma pre-commit hook to a newer beta release in the pre-commit configuration.
  • Bump pyroma revision from 5.0.1 to 5.1b1 in the pre-commit config
  • Preserve pyroma hook setup, including the poetry additional dependency
.pre-commit-config.yaml

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

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've left some high level feedback:

  • Consider whether you really want to pin pyroma to a pre-release (5.1b1); if you prefer more predictable behavior in CI, it may be safer to stay on a stable release unless you specifically need a feature from the beta.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Consider whether you really want to pin `pyroma` to a pre-release (`5.1b1`); if you prefer more predictable behavior in CI, it may be safer to stay on a stable release unless you specifically need a feature from the beta.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@codecov

codecov Bot commented Jul 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (82d1831) to head (a49730b).

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #306   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines          177       177           
  Branches        15        15           
=========================================
  Hits           177       177           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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