Skip to content

chore: re-render the usage file for clap_usage 4 - #670

Merged
jdx merged 1 commit into
mainfrom
claude/render-usage-v4
Jul 26, 2026
Merged

chore: re-render the usage file for clap_usage 4#670
jdx merged 1 commit into
mainfrom
claude/render-usage-v4

Conversation

@jdx

@jdx jdx commented Jul 26, 2026

Copy link
Copy Markdown
Owner

Fixes the build job on main, failing since f161795 with 'mise run render' produced changes.

Cause

#666 bumped clap_usage 2 → 4 (usage-lib 2.18.2 → 4.0.0). The new major version serializes a multi-paragraph long_help as a KDL raw string rather than one quoted line with escaped newlines.

The only two flags in the CLI with a multi-paragraph long_help are --ready-pattern and --relay-token, on the hidden log-sink command — 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 on main, and pitchfork.usage.kdl has been stale since.

This PR

mise run render, nothing else. Generated output, no source changes:

 pitchfork.usage.kdl | 12 ++++++++++--

Worth noting

mise.toml pins usage = "latest" for the CLI-side renderer, while clap_usage is a pinned crate dependency. The two can drift apart without any PR touching Cargo.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.kdl so it matches clap_usage 4 output. No Rust or CLI behavior changes.

On the hidden log-sink command, --ready-pattern and --relay-token now use KDL raw-string long_help blocks (#"""..."""#) instead of one quoted line with \n escapes. 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.

#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>
@coderabbitai

coderabbitai Bot commented Jul 26, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@jdx, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 19 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 77554955-a49e-47c3-8498-8a497840dc42

📥 Commits

Reviewing files that changed from the base of the PR and between f161795 and 573b184.

📒 Files selected for processing (1)
  • pitchfork.usage.kdl

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@greptile-apps

greptile-apps Bot commented Jul 26, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Re-renders the generated CLI usage specification so the two multi-paragraph log-sink flag descriptions use clap_usage 4's multiline KDL raw-string format.

Confidence Score: 5/5

The 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

Filename Overview
pitchfork.usage.kdl Converts two generated long-help values from escaped quoted strings to equivalent valid multiline KDL raw strings without changing their text.

Reviews (1): Last reviewed commit: "chore: re-render the usage file for clap..." | Re-trigger Greptile

@jdx
jdx enabled auto-merge (squash) July 26, 2026 00:47
@jdx
jdx merged commit 579df83 into main Jul 26, 2026
13 checks passed
@jdx
jdx deleted the claude/render-usage-v4 branch July 26, 2026 00:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant