feat: adopt release-please for per-plugin versioning and releases

[drewdrewthis]

Puts release-please in place so plugin versions are never bumped by hand again.

Why now

Installed plugins are cached per version at plugins/cache/<owner>/<plugin>/<version>/. A change that ships without a version bump never reaches an already-installed box.

That is exactly what just happened. PR #25 landed the gate-fork model: sonnet pin but left procedures at 0.2.1. Measured on this machine after the merge:

• cached procedures/0.2.1/skills/how-do-i/SKILL.md had no model: line at all (diff vs origin/main shows the three pin lines absent);
• a live /how-do-i fork ran all 39 calls on claude-opus-5, the parent session model, not sonnet.

The repo had no .github/workflows/ at all, so nothing caught the missing bump. PR #29 is the one-line hotfix; this PR is the fix for the class.

What this sets up

• Manifest mode, one independently versioned + tagged package per plugin (<plugin>-v<version>) — all four: procedures, delegation, about-my-person, take-note.
• extra-files json updater on each .claude-plugin/plugin.json $.version. That is the field an install actually resolves; there is no package.json here, so the stock updaters do not apply.
• separate-pull-requests: true — a procedures fix does not drag the other three into a release.
• CONTRIBUTING gains a versioning section, including the trap worth stating out loud: a behaviour change committed as chore: or docs: produces no release and therefore no bump, so it stays invisible to every installed box.

Verification

• jq -e . parses both JSON files; yaml.safe_load parses the workflow.
• All 4 manifest keys resolve to a real <pkg>/.claude-plugin/plugin.json.
• Manifest values match the current on-main versions exactly (procedures 0.2.1, other three 0.1.0) — seeded from reality, so the first release PR computes from real history instead of re-releasing.
• diff of config packages keys vs manifest keys — identical.

Not verified: no release PR has been generated yet: that only happens once this is on main. The first push to main after merge should open one.

Merge order

Independent of #29 — and self-healing either way. If #29 merges first, plugin.json reads 0.2.2 while the manifest says 0.2.1; release-please then computes 0.2.2 from the fix: commit and converges on the next run.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@drewdrewthis, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 0731c247-f98b-47e2-9fcb-aba3a4d323c6

📥 Commits

Reviewing files that changed from the base of the PR and between 6f737d4 and d1568b0.

📒 Files selected for processing (4)

• .github/workflows/release-please.yml
• .release-please-manifest.json
• CONTRIBUTING.md
• release-please-config.json

---

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