chore: release 0.9.2 - #169
Conversation
Ships the reaction-pipeline fixes from #168. buddy_react reactions written under a different session id than the statusline reads are now adopted rather than clobbered by the canned pool. Hook registrations no longer accumulate on every install: the dedupe filter matched the package name, but the installed path contains neither 'coding-buddy' nor 'claude-buddy', so a dogfooding machine reached eight Stop entries — each duplicate overwriting the previous one's work. A same-turn grace window stops duplicate invocations demoting a reaction the first one just adopted, and adoption is bounded by the statusline's reaction TTL so a stale cross-session reaction cannot surface on a new session. Together these are why reactions kept rendering as canned text no matter how many times the inference path itself was fixed. - package.json
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 21 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. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull request overview
Bumps the package version to 0.9.2 to publish a patch release that includes the already-merged reaction-pipeline fixes referenced in the PR description.
Changes:
- Update
package.jsonversion from0.9.1to0.9.2.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Ships the reaction-pipeline fixes from #168 — the ones that explain why reactions kept appearing as canned text no matter how many times the inference path was fixed.
What ships
Cross-session adoption. The MCP server resolves
BUDDY_SIDonce at launch; the hook and statusline resolve it per invocation. When they diverge,buddy_reactwrote a real model-authored reaction into a file nothing rendered, and the hook — finding nothing fresh in its session — correctly fell back to the pool. Fresh tool reactions are now found across session files and adopted into the current one.Hook registrations no longer accumulate. The dedupe filter matched
coding-buddy/claude-buddy, but the installed path is<state>/app/hooks/buddy-comment.sh— neither string appears, so every install appended another pair. A dogfooding machine reached eightStopentries. Duplicates are not cosmetic: the first invocation adopts the reaction and stamps the marker, the rest judge it stale and overwrite the bubble. Last write wins, so the user always saw canned text.Same-turn grace window, so duplicate invocations cannot demote a reaction the first one just adopted.
Adoption bounded by the statusline's reaction TTL, so a stale cross-session reaction cannot surface on a new session's first turn. Flagged independently by Devin, Copilot and CodeRabbit.
Test determinism: four statusline tests pinned columns but not rows. Once density keyed on rows those became environment-dependent — red on a 30-row developer terminal, structurally invisible in CI where no tty exists.
Why patch
Consumers pin
^0.9.0, which under 0.x resolves to>=0.9.0 <0.10.0. A minor would strand every harness until each pin was updated by hand.🤖 This content was generated with AI assistance using Claude Opus 5.
Note
Release version 0.9.2
Bumps the version field in package.json from
0.9.1to0.9.2.Macroscope summarized 0815554.