Skip to content

[pre-commit.ci] pre-commit autoupdate #3940

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

pre-commit-ci[bot]
Copy link
Contributor

@pre-commit-ci pre-commit-ci bot commented Jul 7, 2025

updates:

Summary by Sourcery

Build:

  • Bump ruff-pre-commit hook version from v0.11.13 to v0.12.2

@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 8898b4e to 9186cf9 Compare July 7, 2025 16:33
Copy link
Contributor

sourcery-ai bot commented Jul 7, 2025

Reviewer's Guide

This PR updates the ruff-pre-commit hook version in the pre-commit configuration by changing the rev from v0.11.13 to v0.12.2.

File-Level Changes

Change Details Files
Bump ruff-pre-commit hook version
  • Update rev field from v0.11.13 to v0.12.2
.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

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

Updates Ruff pre-commit hook from v0.11.13 to v0.12.2, bringing important improvements to syntax error detection and f-string handling.

  • Enhanced detection of CPython syntax errors and compilation-stage errors
  • Improved handling of multiline f-strings with format specifiers for Python 3.13.4+ compatibility
  • Compatible update with no breaking changes or configuration adjustments needed

1 file reviewed, no comments
Edit PR Review Bot Settings | Greptile

@botberry
Copy link
Member

botberry commented Jul 7, 2025

Hi, thanks for contributing to Strawberry 🍓!

We noticed that this PR is missing a RELEASE.md file. We use that to automatically do releases here on GitHub and, most importantly, to PyPI!

So as soon as this PR is merged, a release will be made 🚀.

Here's an example of RELEASE.md:

Release type: patch

Description of the changes, ideally with some examples, if adding a new feature.

Release type can be one of patch, minor or major. We use semver, so make sure to pick the appropriate type. If in doubt feel free to ask :)

Here's the tweet text:

🆕 Release (next) is out! Thanks to pre-commit-ci[bot] for the PR 👏

Get it here 👉 https://strawberry.rocks/release/(next)

Copy link

codecov bot commented Jul 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.75%. Comparing base (10a381d) to head (b48f197).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3940   +/-   ##
=======================================
  Coverage   94.75%   94.75%           
=======================================
  Files         520      520           
  Lines       33947    33947           
  Branches     1759     1759           
=======================================
  Hits        32168    32168           
  Misses       1497     1497           
  Partials      282      282           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link

codspeed-hq bot commented Jul 7, 2025

CodSpeed Performance Report

Merging #3940 will not alter performance

Comparing pre-commit-ci-update-config (b48f197) with main (10a381d)

Summary

✅ 26 untouched benchmarks

updates:
- [github.com/astral-sh/ruff-pre-commit: v0.11.13 → v0.12.3](astral-sh/ruff-pre-commit@v0.11.13...v0.12.3)
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 33ef8f4 to 89c28d8 Compare July 14, 2025 16:31
@bellini666
Copy link
Member

Being updated in #3926 (comment)

@bellini666 bellini666 closed this Jul 15, 2025
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.

2 participants