chore: bump mostro-core to 0.14.1 - #181
Conversation
Aligns the CLI with mostrod v0.18.0, which already ships mostro-core 0.14.1. Staying on 0.13.0 meant any message carrying an action added in 0.14.x (e.g. the Cashu escrow actions) failed deserialization and was silently dropped — the exact hazard the protocol spec warns about in pay_bond_invoice.md. Transport::GiftWrap is now deprecated upstream (mostro/#786); the CLI keeps it as the v1 fallback until mostrod v0.19.0 removes the path, so the single test-side use gets a scoped #[allow(deprecated)].
|
No actionable comments were generated in the recent review. 🎉 ℹ️ 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 (2)
WalkthroughThe PR upgrades ChangesDependency and transport compatibility
Estimated code review effort: 1 (Trivial) | ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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
mostro-corefrom 0.13.0 to 0.14.1 (crates.io), aligning the CLI with mostrod v0.18.0 which already ships 0.14.1.AddCashuEscrow,CashuEscrowLocked,CashuPmSignature) failed deserialization and was silently dropped — the exact migration hazard the protocol spec warns about inpay_bond_invoice.md.Transport::GiftWrapis now deprecated upstream (mostro#786). The CLI intentionally keeps it as the v1 fallback until mostrod v0.19.0 removes the path, so the single test-side use gets a scoped#[allow(deprecated)]with a note.No API changes were needed: the whole test suite and clippy pass clean against 0.14.1.
Test plan
cargo build --release— cleancargo test --release— all suites green (~100 tests)cargo clippy --release --all-targets— no warningsSummary by CodeRabbit