prepare 0.10.1 release

[0xalpharush]

Summary by CodeRabbit

• New Features
  • Introduced a new detector for identifying out-of-order retryable transactions.
• Documentation
  • Updated README with information on the new detector.
• Chores
  • Updated the application version to 0.10.1.
  • Adjusted dependency version for better compatibility and performance.

[coderabbitai]

Walkthrough

This update introduces a new feature for detecting out-of-order retryable transactions and makes minor adjustments to dependencies. Specifically, it adds a new detector to the system and updates the project's version alongside a specific dependency to ensure compatibility and enhance functionality.

Changes

Files	Changes
README.md	Added a new detector out-of-order-retryable.
setup.py	Updated version to "0.10.1" and adjusted crytic-compile dependency version from ">=0.3.5,<0.4.0" to ">=0.3.6,<0.4.0".

🐰✨
In the realm of code, where logic is king,
A new detector's born, its praises we sing.
With dependencies tight and versions anew,
Onward we hop, to bugs we say "shoo".
A leap and a bound, our updates take flight,
In the glow of the moon, we code through the night.
🌙💻

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-tests for this file.
• 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 tests 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 from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

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

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between ecc7a4f and 7563def.

Files selected for processing (2)

• README.md (1 hunks)
• setup.py (1 hunks)

Additional comments: 3

setup.py (2)

• 11-11: The version of the software has been updated to "0.10.1". This change is consistent with the PR's objective to prepare for a new release. Ensure that all related documentation and version references throughout the project are also updated to reflect this new version.
• 18-18: The dependency version for "crytic-compile" has been updated to ">=0.3.6,<0.4.0". This change ensures compatibility with the latest features or fixes introduced in "crytic-compile" version 0.3.6. It's important to verify that this version update does not introduce any breaking changes or incompatibilities with the current codebase.

README.md (1)

• 156-156: The addition of the out-of-order-retryable detector to the README.md file is consistent with the PR's objective to introduce new features. This update enhances the documentation by informing users about the new detector's capabilities. Ensure that the link provided in the description is accessible and leads to the correct documentation page.