Skip to content

Feat: Prepare v2.0.0 breaking API cleanup and release#129

Merged
mxsm merged 1 commit into
mainfrom
feat-2.0.0-breaking-release
Jun 20, 2026
Merged

Feat: Prepare v2.0.0 breaking API cleanup and release#129
mxsm merged 1 commit into
mainfrom
feat-2.0.0-breaking-release

Conversation

@mxsm

@mxsm mxsm commented Jun 20, 2026

Copy link
Copy Markdown
Owner

Closes #128.

Summary:

  • Bump crate metadata and docs to v2.0.0.
  • Remove deprecated safe byte constructors from CheetahString while keeping checked and explicit unsafe constructors.
  • Make CheetahString::from_string use owned mutable storage by default.
  • Keep fuzz lock metadata aligned with v2.0.0.

Verification:

  • cargo fmt -- --check
  • cargo clippy --all-targets --all-features -- -D warnings
  • cargo test --all-features
  • cargo test --no-default-features
  • cargo test --no-default-features --features "serde bytes simd"
  • cargo package --allow-dirty
  • cargo check --manifest-path fuzz\Cargo.toml --bins

@coderabbitai

coderabbitai Bot commented Jun 20, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@mxsm, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 18 minutes and 26 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 73224dc5-fbf4-4fa6-bdbe-38f67e10441a

📥 Commits

Reviewing files that changed from the base of the PR and between b0fbb68 and 60161f2.

⛔ Files ignored due to path filters (1)
  • fuzz/Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (7)
  • .github/workflows/release.yml
  • Cargo.toml
  • README.md
  • bench-results/README.md
  • src/cheetah_string.rs
  • src/lib.rs
  • tests/mutation.rs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat-2.0.0-breaking-release

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@mxsm mxsm merged commit 1df7e78 into main Jun 20, 2026
7 checks passed
@mxsm mxsm deleted the feat-2.0.0-breaking-release branch June 20, 2026 08:40
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.

Feat: Prepare v2.0.0 breaking API cleanup and release

1 participant