chore: move updatecli manifest validate out of experimental - #10586
Conversation
Signed-off-by: Olblak <me@olblak.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Important Review skippedReview was skipped as selected files did not have any reviewable changes. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe ChangesManifest validation availability
Estimated code review effort: 2 (Simple) | ~8 minutes Merge Risk: ⚪ Minimal · up to Manifest validation is available without experimental mode, and the E2E suite includes checks for both valid and invalid manifests. No actionable merge risk is evident. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
Move
updatecli manifest validatenot experimental anymoreTest
To test this pull request, you can run the following commands:
make testAdditional Information
Checklist
Tradeoff
Potential improvement
Summary by CodeRabbit
manifest validateis no longer marked experimental and can be run without the--experimentalflag.