chore(ci): stop release-please from running automatically

[yordis]

• The cargo-workspace plugin hardcodes the Cargo.toml lookup at the repo root, but our workspace lives at rsworkspace/, so release-please fails on every push to main. Pausing the automatic trigger avoids the recurring red builds until the upstream fix lands.

Refs:

• fix(ci): add cargoWorkspacePath to cargo-workspace plugin #58
• feat: add cargoWorkspacePath option to cargo-workspace plugin googleapis/release-please#2682

[cursor]

PR Summary

Low Risk
CI-only workflow trigger change with no application or deployment logic affected.

Overview
Release Please no longer runs on every push to main. The workflow is triggered only via workflow_dispatch (manual run).

Automatic pushes were disabled because the cargo-workspace plugin looks for Cargo.toml at the repo root while this repo’s workspace is under rsworkspace/, which caused recurring failed runs (Failed to find file: Cargo.toml). A TODO in the workflow documents re-enabling the push trigger after upstream support lands, with links to the internal PR and googleapis/release-please#2682.

^{Reviewed by Cursor Bugbot for commit 669b544. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Warning

Review limit reached

@yordis, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 20 minutes and 10 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 578f0c9a-c6bf-48c4-9537-42a24be9ffc4

📥 Commits

Reviewing files that changed from the base of the PR and between fac2882 and 669b544.

📒 Files selected for processing (1)

• .github/workflows/release-please.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch yordis/munich-v1

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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