chore: bump versions for release -- iii(iii/v0.12.0)#1650
Conversation
Manually cut to 0.12.0 stable. Resets the version state inflated by successive minor+next runs that took the base from 0.11.7 to 0.14.0 without intervening stable releases.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (7)
📝 WalkthroughWalkthroughVersion numbers are synchronized across the workspace and all published SDKs from pre-release versions to 0.12.0. The workspace Cargo manifest, Rust crate packages (engine, console, SDK), and Node.js/Python SDK packages are all bumped in a single coordinated update. ChangesCross-platform Version Synchronization
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
Summary
0.14.0-next.1to0.12.0(Python PEP 440 form:0.12.0).Cargo.lockso all 6 workspace crates resolve to0.12.0.After merging this, tag
iii/v0.12.0on the merge commit to trigger the release pipeline.Test plan
iii/v0.12.0tag and confirmrelease-iii.ymlpublishes to crates.io, npm (latest), PyPI, Docker, and HomebrewSummary by CodeRabbit