Skip to content

Release totp-rfc 0.1.2 - #4

Merged
copyleftdev merged 1 commit into
mainfrom
agent/release-v0.1.2
Jul 30, 2026
Merged

Release totp-rfc 0.1.2#4
copyleftdev merged 1 commit into
mainfrom
agent/release-v0.1.2

Conversation

@copyleftdev

Copy link
Copy Markdown
Owner

What changed

  • Bumps totp-rfc from 0.1.1 to 0.1.2.
  • Aligns the root and ctgrind harness lockfiles.
  • Documents the security-first positioning and crates.io metadata update in the changelog.

Why

The hardened README and repository positioning are already merged. crates.io metadata is immutable per published version, so v0.1.2 is required for the improved description and constant-time/no-std keywords to become visible in registry search.

Impact

Metadata-only patch release. There are no API, implementation, behavior, or dependency changes.

Validation

  • ./scripts/release-check.sh v0.1.2
  • cargo +stable clippy --all-targets --all-features --locked -- -D warnings
  • RUSTDOCFLAGS='-D warnings' cargo +stable doc --no-deps --all-features --locked
  • cargo +1.85.0 check --all-targets --all-features --locked
  • cargo deny check
  • cargo +stable publish --dry-run --locked
  • Package: 45 files, 145.7 KiB unpacked, 41.5 KiB compressed

@coderabbitai

coderabbitai Bot commented Jul 30, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@copyleftdev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 21 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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

How do review limits work?

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

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, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 91edfbf0-1cb7-4431-8353-177ab2ff3625

📥 Commits

Reviewing files that changed from the base of the PR and between 67cf69b and 2f762c9.

⛔ Files ignored due to path filters (2)
  • Cargo.lock is excluded by !**/*.lock
  • tools/ctgrind-harness/Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (2)
  • CHANGELOG.md
  • Cargo.toml

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.

@copyleftdev
copyleftdev marked this pull request as ready for review July 30, 2026 22:49
@copyleftdev
copyleftdev merged commit dcb159c into main Jul 30, 2026
5 checks passed
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