chore: release 0.9.4 - #176
Conversation
0.9.3 was published from the release commit, before the version-field fixes merged, so its tarball still carried plugin manifests at 0.8.0 and an MCP handshake at 0.6.0. Nothing consuming the published package could see correct versions. This ships them. Contents since 0.9.3: - #173 synced the plugin manifests and the MCP handshake version. - #174 added scripts/sync-version.ts, a CI drift check, and the npm version lifecycle hook, so this bump updated all three manifests in one command. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H2GXsqpMvUhxBSNabSqZdk
|
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: 18 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. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Pull request overview
Release bump to ensure the published package and Claude plugin manifests advertise the correct version (0.9.4), addressing prior version-drift in shipped artifacts.
Changes:
- Bump
package.jsonversion from0.9.3to0.9.4. - Bump
.claude-plugin/plugin.jsonversion to0.9.4. - Bump
.claude-plugin/marketplace.jsonversion fields to0.9.4.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| package.json | Updates the package’s published version to 0.9.4. |
| .claude-plugin/plugin.json | Keeps the Claude plugin manifest version aligned with the package version. |
| .claude-plugin/marketplace.json | Keeps marketplace metadata/plugin version fields aligned with the package version. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
0.9.3 shipped a tarball that lied about itself. It was published from the release commit, before the version-field fixes merged, so the published package still carries:
.claude-plugin/plugin.json→0.8.0.claude-plugin/marketplace.json→0.8.0server/index.ts→0.6.0Verified by unpacking
npm pack @ramarivera/coding-buddy@0.9.3. Nothing consuming the published package can see a correct version. This release ships them.Contents since 0.9.3
scripts/sync-version.ts, a CI drift check, and the npmversionlifecycle hook.#174 earned its keep immediately: this bump was
bun run sync-versionand all three manifest fields moved in one command.server/index.tsneeded no edit at all since it now importspkg.version.sync-version --check→ 0.bun test→ 475 pass, 0 fail.🤖 Created with the help of AI (Claude Opus 5).
Note
Release version 0.9.4
Bumps the version from
0.9.3to0.9.4in package.json, plugin.json, and marketplace.json.Macroscope summarized 56a753b.