chore: prepare release v3.0.1 - #446
Closed
freshtonic wants to merge 1 commit into
Closed
Conversation
📝 WalkthroughWalkthroughThe workspace package version changed to ChangesRelease metadata
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
freshtonic
force-pushed
the
chore/prepare-3.1.0
branch
from
August 5, 2026 12:00
d235c5d to
4d849ec
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CHANGELOG.md`:
- Around line 9-10: Update CHANGELOG.md so the top-level [Unreleased] section
contains a user-facing entry for this change under the appropriate Keep a
Changelog subsection, or explicitly document a release-specific exception before
the 3.1.0 entries.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: d9049819-f4c6-4565-85d2-6677479250d0
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (2)
CHANGELOG.mdCargo.toml
Contributor
Author
|
Superseded by a correctly-named branch — same commit, new PR incoming. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares the 3.0.1 release, following the same shape as the 3.0.0 prep (#444).
Version
[workspace.package] versionbumped3.0.0→3.0.1in the rootCargo.toml, withcargo update --workspacerun soCargo.lockmatches (only the workspace crates' own versions change).Changelog
[Unreleased]content is now the## [3.0.1] - 2026-08-05section: 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.[Unreleased]still compared fromv2.2.4and[3.0.0]had no link at all. Both now resolve, and[3.0.1]is added.Verification
mise run check— exit 0.