[pre-commit.ci] pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/astral-sh/ruff-pre-commit: v0.15.15 → v0.15.16
• github.com/rvben/rumdl-pre-commit: v0.2.4 → v0.2.9

Summary by Sourcery

Update pre-commit hook versions for linting tools.

Build:

• Bump ruff-pre-commit from v0.15.15 to v0.15.16 in the pre-commit configuration.
• Bump rumdl-pre-commit from v0.2.4 to v0.2.9 in the pre-commit configuration.

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
.pre-commit-config.yaml	1% smaller

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates pinned versions of two pre-commit hooks (ruff and rumdl) in .pre-commit-config.yaml to their latest specified releases, with no other configuration changes.

File-Level Changes

Change	Details	Files
Update ruff pre-commit hook to v0.15.16	Bump the ruff-pre-commit repo revision from v0.15.15 to v0.15.16 for the ruff-check hook Keep existing hook IDs, excludes, and arguments unchanged to rely on upstream defaults in the new version	.pre-commit-config.yaml
Update rumdl pre-commit hook to v0.2.9	Bump the rumdl-pre-commit repo revision from v0.2.4 to v0.2.9 Retain the existing rumdl hook configuration without additional options or excludes	.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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

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 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (df62041) to head (72fb688).

Additional details and impacted files

@@            Coverage Diff            @@
##           develop      #156   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines          398       398           
  Branches        27        27           
=========================================
  Hits           398       398           

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

[greptile-apps]

Greptile Summary

This is an automated pre-commit dependency update generated by pre-commit.ci, bumping two linter versions in .pre-commit-config.yaml.

• ruff-pre-commit bumped from v0.15.15 → v0.15.16 (patch release)
• rumdl-pre-commit bumped from v0.2.4 → v0.2.9 (minor release)

Confidence Score: 5/5

Safe to merge — only two pre-commit tool version bumps with no changes to project logic or configuration behavior.

The change is limited to version strings in .pre-commit-config.yaml. Both updates are minor/patch releases generated by the official pre-commit.ci automation. No project code, tests, or functional configuration is touched.

No files require special attention.

Important Files Changed

Filename	Overview
.pre-commit-config.yaml	Bumps ruff-pre-commit from v0.15.15 to v0.15.16 and rumdl-pre-commit from v0.2.4 to v0.2.9 — routine automated version bumps with no logic changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[pre-commit.ci bot] --> B[Detects new tool versions]
    B --> C[ruff-pre-commit\nv0.15.15 → v0.15.16]
    B --> D[rumdl-pre-commit\nv0.2.4 → v0.2.9]
    C --> E[Updated .pre-commit-config.yaml]
    D --> E
    E --> F[Pre-commit hooks run on future commits\nwith updated linter versions]

Loading

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

[llamapreview]

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