docs(readme): fix two stale claims (published box + explorer dep)#18
Conversation
1. Roadmap "Publish to crates.io once stabilises" was unchecked, but v0.1.0-alpha.0 is on crates.io since 2026-05-12 (verified via `crates.io/api/v1/crates/sentrix-grpc-wasm/versions`). Ticked the box + linked the crate. 2. Status said "used in production by sentrix-explorer-v2". Verified explorer-v2's Cargo.toml: no `sentrix-grpc-wasm` dep — explorer-v2 depends on `sentrix-proto` directly, same as this crate does. They are SIBLING consumers of sentrix-proto, not parent/child. Reframed to capture the actual lineage: grpc-wasm was born inside explorer-v2 then extracted as a reusable wrapper.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe README documentation was updated to reflect the release of Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
12 of N. Fixed: (1) Roadmap had
Publish to crates.ioas unchecked but v0.1.0-alpha.0 is live on crates.io since 2026-05-12. (2) Status claimed explorer-v2 depends on this crate — verified Cargo.toml shows it does NOT; both are sibling consumers of sentrix-proto. Reframed to capture the actual extraction lineage.Summary by CodeRabbit
Documentation