chore(release): bump workspace to 0.4.0-rc.1 (#192)#238
Conversation
First release candidate of the 0.4.0 line. The minor bump is mandated by the MSRV move from 1.92 to 1.95 (#198) — MSRV is part of the semver promise for a library/tool and a non-additive change requires a minor step. See docs/ci/rust-1.95-rollout.md for the policy. Cargo.toml [workspace.package].version 0.3.0-rc.2 -> 0.4.0-rc.1 Cargo.toml [workspace.dependencies] pins same bump for all 13 intra-workspace crates CHANGELOG.md The contents of `[Unreleased]` graduate to `[0.4.0-rc.1] - 2026-05-12` with a one-paragraph release summary citing the major threads (MSRV, lint floor, Clippy ratchets, no-panic baseline + check + release gate, ripr advisory lane, policy receipts, macOS flake stabilisation). A new empty `[Unreleased]` header sits above the 0.4.0-rc.1 block. The forward-looking "Planned — Rust 1.95 / 0.4.0 Quality Rollout" bullet list (15 items) is replaced by a short "Carry-over to follow" section enumerating what is deliberately deferred from rc.1: - mutation-workflow crate-list expansion to the full trust-critical surface, - `duration_suboptimal_units` activation (204-site cleanup), - `engine/parallel/` Mutex-poisoning posture (~35 sites in the no-panic baseline), - CI lane routing changes documented in test-evidence-lanes.md, - final release dry-run proof against the actual tag-push pipeline. Cargo.lock regenerated by `cargo build` No code changes. `cargo build --workspace` and `cargo clippy --workspace --all-targets -- -D warnings` pass; file-policy clean in blocking-allowlist mode. Refs #109 (master tracking) and #192.
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
✨ 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 |
|
Droid finished @EffortlessSteven's task —— View job Droid is reviewing code and running a security check… |
Summary
First release candidate of the 0.4.0 line. Mechanical version bump driven by the MSRV move from 1.92 to 1.95 (#198) — MSRV is part of the semver promise for a library/tool, so a non-additive change requires a minor-version step.
What changed
Cargo.toml[workspace.package].version—0.3.0-rc.2→0.4.0-rc.1Cargo.toml[workspace.dependencies]pins — all 13 intra-workspace crates bumped to0.4.0-rc.1Cargo.lockregenerated viacargo build --workspaceCHANGELOG.md:[Unreleased]graduate to[0.4.0-rc.1] - 2026-05-12with a one-paragraph release summary citing the major threads.[Unreleased]header above the 0.4.0-rc.1 block.Carry-over to follow (deferred from rc.1)
duration_suboptimal_unitsClippy lint activation (204-site cleanup).engine/parallel/.lock().unwrap()Mutex-poisoning posture (~35 sites in the no-panic baseline).docs/ci/test-evidence-lanes.md.Test plan
cargo build --workspace— cleancargo clippy --workspace --all-targets -- -D warnings— cleancargo fmt --all -- --check— cleancargo xtask check-file-policy --mode blocking-allowlist—unreceipted=0Refs #109 (master tracking) and #192.