docs: remove stale source-build notices - #859
Conversation
Signed-off-by: Ryan Lempka <rlempka@nvidia.com>
|
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: NVIDIA-NeMo/Switchyard/.coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (4)
💤 Files with no reviewable changes (4)
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review. WalkthroughFour documentation pages no longer contain notices that examples require unreleased features or a source build. ChangesRouting documentation
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to No actionable issue with the notice cleanup was established. The change is mergeable after normal checks. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
A rabbit read the routing guide, Comment |
Remove the stale source-build notices now that v0.3.0 is published.
Validated all four documented configurations with the crates.io v0.3.0 server using
--dry-run. The strict docs build also passes.Summary by CodeRabbit