chore: re-render the usage file for clap_usage 4 - #670
Conversation
#666 bumped clap_usage 2 -> 4, which writes a multi-paragraph long_help as a KDL raw string instead of one quoted line with escaped newlines. The only two flags with such a help text arrived in #667, twelve minutes earlier, so neither PR rendered the combination and main's render check has failed since they met. Generated output only. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 19 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
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 |
Greptile SummaryRe-renders the generated CLI usage specification so the two multi-paragraph Confidence Score: 5/5The PR appears safe to merge with no actionable defects identified. The generated usage-file changes preserve the existing help text while adopting the multiline KDL representation already used elsewhere in the file. Important Files Changed
Reviews (1): Last reviewed commit: "chore: re-render the usage file for clap..." | Re-trigger Greptile |
Fixes the
buildjob onmain, failing since f161795 with'mise run render' produced changes.Cause
#666 bumped
clap_usage2 → 4 (usage-lib2.18.2 → 4.0.0). The new major version serializes a multi-paragraphlong_helpas a KDL raw string rather than one quoted line with escaped newlines.The only two flags in the CLI with a multi-paragraph
long_helpare--ready-patternand--relay-token, on the hiddenlog-sinkcommand — both added by #667, merged twelve minutes before #666. Each PR rendered cleanly against the tree it was tested on; the combination existed for the first time onmain, andpitchfork.usage.kdlhas been stale since.This PR
mise run render, nothing else. Generated output, no source changes:Worth noting
mise.tomlpinsusage = "latest"for the CLI-side renderer, whileclap_usageis a pinned crate dependency. The two can drift apart without any PR touchingCargo.toml, so this failure mode can recur on an unrelated commit. Pinning the tool would remove that.This PR was generated by Claude Code.
Note
Low Risk
Generated documentation-only change with no runtime or CLI logic impact.
Overview
Regenerates
pitchfork.usage.kdlso it matches clap_usage 4 output. No Rust or CLI behavior changes.On the hidden
log-sinkcommand,--ready-patternand--relay-tokennow use KDL raw-stringlong_helpblocks (#"""..."""#) instead of one quoted line with\nescapes. The help text is unchanged; only serialization format differs after the clap_usage major bump.Reviewed by Cursor Bugbot for commit 573b184. Bugbot is set up for automated code reviews on this repo. Configure here.