chore(email): leave the version bump to Release Control - #980
Conversation
PR #979 raised email/Cargo.toml to 0.2.0 by hand. Release Control owns worker versions: it derives the candidate from the registry base and commits the prepare bump itself, and the hand bump made it plan 0.2.1-rc.1 against a 0.1.7 base, which its prepare step rejected. Back to 0.1.7 so the next release intent (minor) yields 0.2.0-rc.1.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
skill-check — worker0 verified, 69 skipped (no docs/).
Four for four. Nicely done. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe ChangesEmail package version
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: Poem
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 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 |
PR #979 raised
email/Cargo.tomlfrom 0.1.7 to 0.2.0 by hand. Release Control owns worker versions: it derives the candidate from the registry base (0.1.7) and commits theprepare vXbump itself, so the hand bump made it plan0.2.1-rc.1and its prepare step failed at dispatch (prepare_release:email: dispatch outcome is unknown), leaving theworker:emaillock held.This puts the manifest back at 0.1.7 (Cargo.toml + Cargo.lock only). The intended release stays 0.2.0: pick the minor stable goal in Release Control and it will derive
0.2.0-rc.1. The README already documents 0.2.0.Summary by CodeRabbit