chore(release): bump workspace to 0.3.0-rc.2#146
Conversation
Promotes the [Unreleased] CHANGELOG section to [0.3.0-rc.2] dated 2026-04-18 and bumps the workspace version (including all intra- workspace dependency version pins) to match. Release candidate covering 29 commits of nine-competency roadmap work: #90, #91, #92, #93, #94, #95, #96, #97, #98, #99. Trust-core queue fully collapsed; next milestone is operator-side real Recover rehearsal before tagging 0.3.0 stable. Does not tag or publish — leave that to the release cut.
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 6 minutes and 46 seconds. ⌛ 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 (2)
📒 Files selected for processing (3)
✨ 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 |
There was a problem hiding this comment.
Code Review
This pull request updates the version of the shipper workspace and its internal crates from 0.3.0-rc.1 to 0.3.0-rc.2 across Cargo.toml, Cargo.lock, and CHANGELOG.md. A suggestion was made to retain an empty [Unreleased] section in the changelog to facilitate future documentation of changes.
| and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). | ||
|
|
||
| ## [Unreleased] | ||
| ## [0.3.0-rc.2] - 2026-04-18 |
There was a problem hiding this comment.
When promoting the [Unreleased] section to a specific version, it is a best practice to add a new, empty [Unreleased] section at the top of the file. This ensures that future contributions have a designated place to be documented immediately after the release chore is merged.
| ## [0.3.0-rc.2] - 2026-04-18 | |
| ## [Unreleased] | |
| ## [0.3.0-rc.2] - 2026-04-18 |
CI on the rc.2 bump PR broke the help_yank snapshot. Root cause: the `--version` docstring hardcoded `0.3.0-rc.1` as an example, and the snapshot test normalizes CARGO_PKG_VERSION → [VERSION]. On rc.1 the literal matched CARGO_PKG_VERSION and normalized to [VERSION]; on rc.2 the literal no longer matches, so the snapshot sees a raw `0.3.0-rc.1` and diverges. Fix: use `1.2.3` as a stable, version-independent example so the docstring doesn't need to track every rc bump. Snapshot updated to match. All 20 help-snapshot tests pass locally.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Summary
0.3.0-rc.1→0.3.0-rc.2.[Unreleased]CHANGELOG section to[0.3.0-rc.2] - 2026-04-18.Cargo.lockaccordingly.Why rc.2 (not 0.3.0 stable)
The 29 commits since rc.1 include substantial new surface (rehearse, yank/fix-forward, OIDC, three-crate split, reconcile). The code is tested, but the operator-side real Recover rehearsal still hasn't been run on current
main— that's the last trust check before stable.Not in this PR
git tag -a v0.3.0-rc.2 -m "..."; git push origin v0.3.0-rc.2)cargo publish(requires your token; publish order isshipper-core→shipper-cli→shipperplus any changed microcrates)Test plan
cargo check --workspacecleancargo test -p shipper-core shipper_version— version-handling tests green