chore: release v0.1.2

[unclesp1d3r]

Summary

Cuts v0.1.2 to publish crate dependency bumps that were merged as chore(deps) (and thus skipped by release-plz release_commits) and never reached crates.io.

• thiserror → 2.0.18
• windows → 0.62.2
• proptest (dev) → 1.10
• No library code changes since v0.1.1 — src/ is unchanged; these are semver-compatible dependency-minimum bumps plus CI/tooling.
• Also corrects the maintainer author email in Cargo.toml (unclespid3r → unclesp1d3r).

On merge, the release-plz release job publishes v0.1.2 to crates.io and tags it (cargo-dist then cuts the GitHub release).

Test plan

• CI green (Code Quality + Test (Windows))
• After merge: release-plz publishes v0.1.2 to crates.io and creates the v0.1.2 tag

[coderabbitai]

Warning

Review limit reached

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

More reviews will be available in 22 minutes and 40 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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 0672f460-0b0b-47a7-9830-27c525a1eda6

📥 Commits

Reviewing files that changed from the base of the PR and between 713a743 and 870b2fc.

📒 Files selected for processing (2)

• CHANGELOG.md
• Cargo.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v0.1.2

---

_{Comment @coderabbitai help to get the list of available commands.}

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🔴 🚦 Auto-queue

Waiting for

• label = release

This rule is failing.

When all merge protections are satisfied and these conditions match, this pull request will be queued automatically.

• any of:
  • all of:
    • author = dependabot[bot]
    • base = main
    • label != do-not-merge
  • all of:
    • author = dosubot[bot]
    • base = main
    • label != do-not-merge
  • all of:
    • author = release-plz[bot]
    • label = release
    • base = main

🟢 CI must pass

Wonderful, this rule succeeded.

• #commits-behind <= 3
• check-success = Code Quality
• check-success = Test (Windows)

[unclesp1d3r]

@Mergifyio queue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-06-24 01:49 UTC · Rule: default · triggered by the @mergifyio queue command
• ✅ Checks passed · on draft merge queue: queuing main (40f1933) and #19 together #25
• ✅ Merged — 2026-06-24 01:54 UTC · at 870b2fc62f7f2de3b8e2d1d22d9008aba02bad81 · squash

This pull request spent 4 minutes 39 seconds in the queue, including 4 minutes running CI.

Required conditions to merge

• check-success = Code Quality
• check-success = Test (Windows)
• all of [🛡 Merge Protections rule CI must pass]:
  • #commits-behind <= 3
    • chore: release v0.1.2 #19
  • check-success = Code Quality
  • check-success = Test (Windows)
• any of [🛡 GitHub repository ruleset rule main]:
  • check-success = DCO
  • check-neutral = DCO
  • check-skipped = DCO
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!