[pre-commit.ci] pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/asottile/pyupgrade: v3.16.0 → v3.17.0
• github.com/psf/black: 24.4.2 → 24.8.0
• github.com/PyCQA/flake8: 7.1.0 → 7.1.1

Summary by CodeRabbit

• New Features
  • Updated dependencies for code formatting and linting tools to their latest versions, enhancing code quality and performance.
• Bug Fixes
  • Improvements from the latest versions of pyupgrade, black, and flake8 may resolve previous issues and enhance functionality.

[coderabbitai]

Walkthrough

The recent updates to the .pre-commit-config.yaml file involve upgrading key code quality tools. Notably, pyupgrade moves from version 3.16.0 to 3.17.0, enhancing Python code modernization capabilities. The black code formatter is upgraded from 24.4.2 to 24.8.0, introducing new formatting features. Lastly, flake8 linter is updated from 7.1.0 to 7.1.1, ensuring minor updates and fixes. These changes aim to maintain and improve the overall efficiency of the codebase.

Changes

File	Change Summary
.pre-commit-config.yaml	Updated pyupgrade from v3.16.0 to v3.17.0, black from 24.4.2 to 24.8.0, and flake8 from 7.1.0 to 7.1.1.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant PreCommit
    participant Tools

    Developer->>PreCommit: Initiates pre-commit check
    PreCommit->>Tools: Runs updated tools (pyupgrade, black, flake8)
    Tools-->>PreCommit: Returns results
    PreCommit-->>Developer: Displays results

Loading

Poem

🐇 In the garden, code blooms bright,
With pyupgrade taking flight!
Black now paints with newer hues,
While flake8 checks for tiny clues.
A hop, a skip, let’s celebrate,
Our code is fresh—oh, isn’t it great? 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.37%. Comparing base (b4fe7bb) to head (c2c65df).

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@           Coverage Diff           @@
##           master      #43   +/-   ##
=======================================
  Coverage   93.37%   93.37%           
=======================================
  Files           5        5           
  Lines         921      921           
=======================================
  Hits          860      860           
  Misses         61       61           

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

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b4fe7bb and c2c65df.

Files selected for processing (1)

• .pre-commit-config.yaml (2 hunks)

Files skipped from review due to trivial changes (1)

• .pre-commit-config.yaml