Skip to content

chore: release 0.9.4 - #176

Merged
ramarivera merged 1 commit into
mainfrom
chore/bump-0.9.4
Jul 28, 2026
Merged

chore: release 0.9.4#176
ramarivera merged 1 commit into
mainfrom
chore/bump-0.9.4

Conversation

@ramarivera

@ramarivera ramarivera commented Jul 28, 2026

Copy link
Copy Markdown
Owner

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.json0.8.0
  • .claude-plugin/marketplace.json0.8.0
  • MCP handshake in server/index.ts0.6.0

Verified 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

#174 earned its keep immediately: this bump was bun run sync-version and all three manifest fields moved in one command. server/index.ts needed no edit at all since it now imports pkg.version.

sync-version --check → 0. bun test → 475 pass, 0 fail.

🤖 Created with the help of AI (Claude Opus 5).


Open in Devin Review

Note

Release version 0.9.4

Bumps the version from 0.9.3 to 0.9.4 in package.json, plugin.json, and marketplace.json.

Macroscope summarized 56a753b.

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
Copilot AI review requested due to automatic review settings July 28, 2026 04:19
@github-project-automation github-project-automation Bot moved this to Todo in Kanban Jul 28, 2026
@gemini-code-assist

Copy link
Copy Markdown

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown

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: 18 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: c40539d5-b103-4d0e-8432-81a1356a817e

📥 Commits

Reviewing files that changed from the base of the PR and between dd66c49 and 56a753b.

📒 Files selected for processing (3)
  • .claude-plugin/marketplace.json
  • .claude-plugin/plugin.json
  • package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/bump-0.9.4

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

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Open in Devin Review

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.json version from 0.9.3 to 0.9.4.
  • Bump .claude-plugin/plugin.json version to 0.9.4.
  • Bump .claude-plugin/marketplace.json version fields to 0.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.

@ramarivera
ramarivera merged commit 4b7a81c into main Jul 28, 2026
6 checks passed
@github-project-automation github-project-automation Bot moved this from Todo to Done in Kanban Jul 28, 2026
@ramarivera
ramarivera deleted the chore/bump-0.9.4 branch July 28, 2026 04:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants