Bump version to v0.3.0#170
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #170 +/- ##
==========================================
+ Coverage 81.92% 82.16% +0.23%
==========================================
Files 17 17
Lines 6441 6441
==========================================
+ Hits 5277 5292 +15
+ Misses 1164 1149 -15
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe pull request increments the workspace and package versions from 0.2.0 to 0.3.0 across manifests: root Cargo.toml workspace.package, several internal crate versions in [workspace.dependencies], multiple npm package.json files (platform builds and main packages), and updates Node.js tool versions in CI/config (Node 22 → 24). Changes are limited to version and CI-tool entries; no code, paths, or external dependency coordinates were altered. Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 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 |
Node 24's npm (v11) correctly preserves optional dependency stub entries in package-lock.json for packages not yet published to the registry. Node 22's npm (v10) silently dropped them, causing the sync-versions pre-commit hook to fail in CI.
Summary
0.2.0to0.3.0across all crates and npm packagesCargo.tomlworkspace version (source of truth), then ranscripts/sync-versions.jsto propagate to all 10 affected filessync-versions.js --check