docs(cli): document bundle upload --auto-bump

[riderx]

Summary (AI generated)

• Documented bundle upload --auto-bump on the CLI reference (bundle.mdx) with examples and option table entry
• Added the flag to the legacy CLI commands list
• Added a CI/CD note for when package.json version was already uploaded
• Linked the flag from live-updates channels versioning guidance

Motivation (AI generated)

The Capgo CLI now supports --auto-bump to pick the next free semver from a channel's linked bundle (or latest remote app version). Customers need public docs with correct npx @capgo/cli@latest examples before relying on it in CI.

Business Impact (AI generated)

Reduces failed uploads from duplicate bundle versions in CI, lowers support load around version conflicts, and makes Capgo easier to adopt without forcing every pipeline to bump package.json first.

Test Plan (AI generated)

• Confirm /docs/cli/reference/bundle/ shows --auto-bump examples and option row
• Confirm /docs/getting-started/cicd-integration/ auto-bump subsection renders and anchors work
• Confirm channels versioning paragraph links resolve
• Spot-check that examples use npx @capgo/cli@latest (not bunx)

Generated with AI

Made with Cursor

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 24 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: a73b5488-5763-4de3-b6fb-9281a903030f

📥 Commits

Reviewing files that changed from the base of the PR and between 29e488a and 0e897b7.

📒 Files selected for processing (4)

• apps/docs/src/content/docs/docs/cli/commands.mdx
• apps/docs/src/content/docs/docs/cli/reference/bundle.mdx
• apps/docs/src/content/docs/docs/getting-started/cicd-integration.mdx
• apps/docs/src/content/docs/docs/live-updates/channels.mdx

---

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

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_ad2ba030-cb3a-4443-a73c-0aa4e44a3fb6)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[cubic-dev-ai]

No issues found across 4 files

_{Re-trigger cubic}