release: v2.36.5#642
Conversation
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code review is billed via overage credits. To resume reviews, an organization admin can raise the monthly limit at claude.ai/admin-settings/claude-code.
Once credits are available, push a new commit or reopen this pull request to trigger a review.
|
Warning Review limit reached
More reviews will be available in 42 minutes. 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 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (7)
✨ 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 |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c4072b5b87
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".
| "description": "Business operations command center for Claude Code — 59 skills, 21 agents, smart background daemon. Manage communications (WhatsApp/Email/Slack/Telegram), projects, infrastructure (AWS), revenue (Stripe+RevenueCat), e-commerce, marketing, monitoring (Datadog/New Relic/OTEL), voice, and smart home (Homey Pro). Includes /ops:ops-ar A&R (audio analysis + demo verdict cards), /gtm go-to-market planner, /ops:projects portfolio dashboard, /ops:ops-home control surface, and YOLO autonomous mode with 4 parallel C-suite agents.", | ||
| "source": "./claude-ops", | ||
| "version": "2.37.0", | ||
| "version": "2.36.5", |
There was a problem hiding this comment.
For users who already installed the prior 2.37.0 release, this marketplace version makes the new release semver-older than what is cached. I checked the repo’s version resolution paths: claude-ops/scripts/ops-daemon-manager.sh sorts installed cache dirs with sort -V and takes tail -1, and the recap/notifier launchers use the same highest-version pattern, so a cache containing both 2.37.0 and this 2.36.5 will keep resolving the stale 2.37.0 tree and miss the ops-yolo release. The same downgrade is in plugin.json/package.json; this should be renumbered above 2.37.0 before publishing.
Useful? React with 👍 / 👎.
1 participant
Release v2.36.5 (was 2.36.4).
ops-yolo: always consolidate the four C-suite analyses into one master executive-summary.md per run (TL;DR, consensus action, cross-cutting themes, prioritized auto/confirm action list); per-officer files become supporting detail.
🤖 Generated with Claude Code
Note
Low Risk
Metadata and documentation release; no runtime code appears in the diff, with behavioral change described only via changelog/skill docs.
Overview
Cuts a v2.36.5 release by aligning version strings to
2.36.5across the marketplace registry, plugin manifest,package.json, README, and docs badges (replacing2.37.0in those files).CHANGELOG adds
[2.36.5]documenting the product change for this release:/ops:yolomust always merge the four parallel C-suite analyses into oneexecutive-summary.mdper run (TL;DR, consensus action, cross-cutting themes, prioritized auto vs confirm actions), with per-officer markdown kept as supporting detail only.Reviewed by Cursor Bugbot for commit c4072b5. Bugbot is set up for automated code reviews on this repo. Configure here.