Skip to content

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

Merged
cleder merged 1 commit intodevelopfrom
pre-commit-ci-update-config
Apr 1, 2026
Merged

[pre-commit.ci] pre-commit autoupdate#345
cleder merged 1 commit intodevelopfrom
pre-commit-ci-update-config

Conversation

@pre-commit-ci
Copy link
Copy Markdown
Contributor

@pre-commit-ci pre-commit-ci Bot commented Mar 30, 2026

updates:

Summary by Sourcery

Update pre-commit hook versions to their latest patch releases.

Build:

  • Bump ruff-pre-commit hook from v0.15.7 to v0.15.8 in the pre-commit configuration.
  • Bump check-jsonschema hook from 0.37.0 to 0.37.1 in the pre-commit configuration.

updates:
- [github.com/astral-sh/ruff-pre-commit: v0.15.7 β†’ v0.15.8](astral-sh/ruff-pre-commit@v0.15.7...v0.15.8)
- [github.com/python-jsonschema/check-jsonschema: 0.37.0 β†’ 0.37.1](python-jsonschema/check-jsonschema@0.37.0...0.37.1)
@semanticdiff-com
Copy link
Copy Markdown

semanticdiff-com Bot commented Mar 30, 2026

Review changes with Β SemanticDiff

Changed Files
File Status
Β Β .pre-commit-config.yaml Β 0% smaller

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Mar 30, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates pinned versions of two pre-commit hooks (ruff and check-jsonschema) in the pre-commit configuration to their latest patch releases, without any other configuration changes.

File-Level Changes

Change Details Files
Bump ruff-pre-commit hook to the next patch release.
  • Update the ruff-pre-commit repository revision from v0.15.7 to v0.15.8 in the pre-commit configuration.
  • Keep the set of ruff hooks (ruff-check, ruff-format) unchanged.
.pre-commit-config.yaml
Bump check-jsonschema hook to the next patch release.
  • Update the check-jsonschema repository revision from 0.37.0 to 0.37.1 in the pre-commit configuration.
  • Retain the existing set of JSON schema-related hooks (check-github-workflows, check-github-actions) without modification.
.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

@what-the-diff
Copy link
Copy Markdown

what-the-diff Bot commented Mar 30, 2026

PR Summary

  • Updated ruff-pre-commit hook version
    The version of the ruff-pre-commit hook, which helps maintain and improve the quality of the code, has been updated from v0.15.7 to v0.15.8. This could potentially include important upgrades contributing to the optimization of the development workflow.

  • Updated check-jsonschema hook version
    The check-jsonschema hook version, which is used to validate the structure of JSON documents in the project, has been updated from 0.37.0 to 0.37.1. This could bring improvements in detecting structure issues thus ensuring data consistency.

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

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

Hey - I've reviewed your changes and they look great!


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.

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented Mar 30, 2026

Greptile Summary

This is a routine automated pre-commit hook version bump generated by pre-commit.ci. Two linting/validation tools receive minor patch upgrades:

  • astral-sh/ruff-pre-commit: v0.15.7 β†’ v0.15.8 (Ruff linter & formatter)
  • python-jsonschema/check-jsonschema: 0.37.0 β†’ 0.37.1 (JSON schema validation for GitHub workflow/action files and ReadTheDocs config)

Both are patch releases with no breaking changes expected. No application code, tests, or documentation are affected β€” only the developer tooling configuration is updated.

Confidence Score: 5/5

Safe to merge β€” only development tooling versions are bumped, with no impact on application code or behaviour.

Both changes are automated patch-level version bumps for pre-commit hooks. No logic, tests, or production code is touched. No issues were identified during review.

No files require special attention.

Important Files Changed

Filename Overview
.pre-commit-config.yaml Bumps ruff-pre-commit from v0.15.7 to v0.15.8 and check-jsonschema from 0.37.0 to 0.37.1 β€” both are routine patch-level version increments with no structural changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[git commit] --> B[pre-commit hooks]
    B --> C[pre-commit-hooks\ncheck-yaml / check-toml / etc.]
    B --> D[absolufy-imports\nv0.3.1]
    B --> E[ruff-pre-commit\n**v0.15.8** ← bumped]
    B --> F[flake8\n7.3.0]
    B --> G[mypy\nv1.19.1]
    B --> H[validate-pyproject\nv0.25]
    B --> I[pyprojectsort\nv0.4.0]
    B --> J[check-jsonschema\n**0.37.1** ← bumped]
    B --> K[pyroma\n5.0.1]
    B --> L[complexipy\nv5.1.0]
    E -->|ruff-check & ruff-format| M{All hooks pass?}
    J -->|check-github-workflows\ncheck-github-actions\ncheck-readthedocs| M
    M -->|Yes| N[Commit accepted]
    M -->|No| O[Commit blocked]
Loading

Reviews (1): Last reviewed commit: "[pre-commit.ci] pre-commit autoupdate" | Re-trigger Greptile

@github-actions
Copy link
Copy Markdown

Failed to generate code suggestions for PR

Copy link
Copy Markdown

@llamapreview llamapreview Bot left a comment

Choose a reason for hiding this comment

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

Auto Pull Request Review from LlamaPReview

Review Status: Automated Review Skipped

Dear contributor,

Thank you for your Pull Request. LlamaPReview has analyzed your changes and determined that this PR does not require an automated code review.

Analysis Result:

PR only contains version updates and formatting changes

Technical Context:

Version and formatting changes detected, which include:

  • Package version updates
  • Dependency version changes
  • Code formatting adjustments
  • Whitespace modifications
  • Structural formatting changes

We're continuously improving our PR analysis capabilities. Have thoughts on when and how LlamaPReview should perform automated reviews? Share your insights in our GitHub Discussions.

Best regards,
LlamaPReview Team

@codecov
Copy link
Copy Markdown

codecov Bot commented Mar 30, 2026

Codecov Report

βœ… All modified and coverable lines are covered by tests.
βœ… Project coverage is 100.00%. Comparing base (72d3f53) to head (215004d).
⚠️ Report is 2 commits behind head on develop.

Additional details and impacted files
@@            Coverage Diff            @@
##           develop      #345   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           32        32           
  Lines         2709      2709           
  Branches        91        91           
=========================================
  Hits          2709      2709           

β˜” View full report in Codecov by Sentry.
πŸ“’ 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.

@github-actions
Copy link
Copy Markdown

Preparing review...

1 similar comment
@github-actions
Copy link
Copy Markdown

Preparing review...

@cleder cleder merged commit c0eb8ee into develop Apr 1, 2026
48 checks passed
@cleder cleder deleted the pre-commit-ci-update-config branch April 1, 2026 11:51
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.

1 participant