chore: prepare release v3.0.1

[freshtonic]

Prepares the 3.0.1 release, following the same shape as the 3.0.0 prep (#444). (Replaces #446, which sat on a misnamed branch.)

Version

• [workspace.package] version bumped 3.0.0 → 3.0.1 in the root Cargo.toml, with cargo update --workspace run so Cargo.lock matches (only the workspace crates' own versions change).

Changelog

• The [Unreleased] content is now the ## [3.0.1] - 2026-08-05 section: 2 Added, 5 Fixed and 3 Security entries, covering PRs fix(proxy): stop the JSON selector fusion leaking plaintext (CIP-3682) #435, fix(proxy): refuse statements on a legacy eql_v2_encrypted column instead of serving it as plaintext (CIP-3688) #437, fix(mapper): inference hardening — LIMIT/FETCH, UPDATE targets, unmatched statements (CIP-3700) #439, fix(mapper): close inference gaps on AST fields of type-checked statements (CIP-3699) #440, fix(proxy): protocol desync on transformation error after a mapped statement (CIP-3678) #441 and fix(mapper): make the late native fallback for unresolved value nodes fail closed (CIP-3715) #442.
• Also repairs the link references at the bottom of the file, which the 3.0.0 release had left stale: [Unreleased] still compared from v2.2.4 and [3.0.0] had no link at all. Both now resolve, and [3.0.1] is added.

Verification

• mise run check — exit 0.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 56 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: c41d29cf-be6d-4bb4-b769-0f48288c7b41

📥 Commits

Reviewing files that changed from the base of the PR and between 73c6b2e and 4d849ec.

⛔ Files ignored due to path filters (1)

• 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

• X
• Mastodon
• Reddit
• LinkedIn

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