Skip to content

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

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

[pre-commit.ci] pre-commit autoupdate#145
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 minor releases.

Build:

  • Bump ruff-pre-commit hook from v0.15.7 to v0.15.8 in .pre-commit-config.
  • Bump python-jsonschema/check-jsonschema hook from 0.37.0 to 0.37.1 in .pre-commit-config.
  • Bump rvben/rumdl-pre-commit hook from v0.1.58 to v0.1.62 in .pre-commit-config.

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)
- [github.com/rvben/rumdl-pre-commit: v0.1.58 → v0.1.62](rvben/rumdl-pre-commit@v0.1.58...v0.1.62)
@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

Update pinned revisions for several pre-commit hooks (ruff, check-jsonschema, rumdl) to their latest patch versions in .pre-commit-config.yaml.

File-Level Changes

Change Details Files
Bump ruff pre-commit hook revision to the next patch release.
  • Update the ruff-pre-commit repo rev from v0.15.7 to v0.15.8 in the pre-commit configuration
.pre-commit-config.yaml
Bump check-jsonschema pre-commit hook to the next patch release.
  • Update the check-jsonschema repo rev from 0.37.0 to 0.37.1 in the pre-commit configuration
.pre-commit-config.yaml
Bump rumdl pre-commit hook revision to the next patch release.
  • Update the rumdl-pre-commit repo rev from v0.1.58 to v0.1.62 in the pre-commit configuration
.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

@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 (98993ca) to head (2363f07).
⚠️ Report is 2 commits behind head on develop.

Additional details and impacted files
@@            Coverage Diff            @@
##           develop      #145   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines          398       398           
  Branches        27        27           
=========================================
  Hits           398       398           

☔ 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.

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 dependency update generated by pre-commit.ci, bumping three linting/validation tools to their latest patch releases.

  • ruff-pre-commit: v0.15.7v0.15.8 (patch release)
  • check-jsonschema: 0.37.00.37.1 (patch release)
  • rumdl-pre-commit: v0.1.58v0.1.62 (minor bump across four patch versions)

All updates are non-breaking patch/minor increments applied to .pre-commit-config.yaml only. No source code, tests, or configuration beyond the pre-commit toolchain are affected.

Confidence Score: 5/5

Safe to merge — automated patch-level version bumps to pre-commit tooling with no source code changes.

All three updates are minor/patch releases generated by the pre-commit.ci bot. No logic, source code, tests, or breaking API changes are involved.

No files require special attention.

Important Files Changed

Filename Overview
.pre-commit-config.yaml Bumps three pre-commit hook revisions: ruff v0.15.7→v0.15.8, check-jsonschema 0.37.0→0.37.1, rumdl v0.1.58→v0.1.62 — all minor/patch releases with no breaking changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[git commit / pre-commit run] --> B[pre-commit hooks]
    B --> C[ruff-check v0.15.8]
    B --> D[check-jsonschema 0.37.1]
    B --> E[rumdl v0.1.62]
    B --> F[Other hooks unchanged]
    C -->|pass| H[commit accepted]
    D -->|pass| H
    E -->|pass| H
    F -->|pass| H
Loading

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

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

@cleder cleder merged commit 00d3550 into develop Apr 1, 2026
24 checks passed
@cleder cleder deleted the pre-commit-ci-update-config branch April 1, 2026 11:50
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