fix(procedures): bump to 0.2.2 to ship the gate-fork model pin - #29
Merged
Conversation
#25 landed the `model: sonnet` pin on both gate skills but left the plugin version at 0.2.1. Installed plugins are cached per version at plugins/cache/<owner>/<plugin>/<version>/, so a fix that does not bump the version never reaches an already-installed box: measured on this machine after #25 merged, the cached 0.2.1 how-do-i/SKILL.md still had no `model:` line, and a live /how-do-i fork ran all 39 calls on claude-opus-5 (the parent's model) rather than sonnet. Same mechanism and same remedy as 03830b2 ("Bump procedures to 0.1.1 — ships the namespaced-skill-recording fix to version-pinned caches"). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe procedures plugin manifest version was incremented from ChangesProcedures plugin version
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
drewdrewthis
pushed a commit
that referenced
this pull request
Aug 7, 2026
All four manifest entries now match origin/main's plugin.json exactly, so the first release PR computes from real history instead of re-releasing 0.2.2. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
drewdrewthis
added a commit
that referenced
this pull request
Aug 7, 2026
* feat: adopt release-please for per-plugin versioning and releases Installed plugins are cached per version at plugins/cache/<owner>/<plugin>/<version>/, so a change that ships without a version bump never reaches an already-installed box. That is not theoretical: #25 landed the gate-fork `model: sonnet` pin but left procedures at 0.2.1, and a live /how-do-i fork measured after the merge still ran all 39 calls on the parent's model because the cached 0.2.1 copy had no `model:` line. The repo had no workflows at all, so nothing caught it. Manifest mode, one independently versioned+tagged package per plugin (<plugin>-v<version>), with an extra-files json updater pointing at each .claude-plugin/plugin.json `$.version` — that file, not a package.json, is the version an install actually resolves. Manifest is seeded from the current on-main versions, so the first release PR computes from real history rather than re-releasing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * chore: reseed procedures manifest to 0.2.2 after #29 merged All four manifest entries now match origin/main's plugin.json exactly, so the first release PR computes from real history instead of re-releasing 0.2.2. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Ubuntu <ubuntu@ip-10-0-3-222.eu-central-1.compute.internal> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR #25 landed the
model: sonnetpin on both gate skills, but leftplugins/procedures/.claude-plugin/plugin.jsonat0.2.1. Installed plugins are cached per version atplugins/cache/<owner>/<plugin>/<version>/, so a fix that does not bump the version never reaches an already-installed box.Measured after #25 merged
2026-08-07T18:11:12Z.plugins/cache/drewdrewthis/procedures/0.2.1/skills/how-do-i/SKILL.md, mtime13:17:34Z— ~5h older than the merge, anddiffagainstorigin/mainshows the three pin lines simply absent./how-do-ifork at18:17Z— six minutes after the merge — ran all 39 calls onclaude-opus-5, the parent session model. The pin was not in effect.Why this is the right remedy
Same mechanism and same fix as
03830b2— "Bump procedures to 0.1.1 — ships the namespaced-skill-recording fix to version-pinned caches."0.2.1is pinned in exactly one place, so the bump is a one-line change.Verification
bats plugins/procedures/hooks/tests/gate-skill-model.batsonmain→1..3, 3/3 passing — the pin itself is correct onmain; it just cannot reach an installed box without this bump.Follow-up (not in this PR)
Nothing fails when a
skills/- oragents/-touching PR forgets the version bump — that is what let #25 through. Worth a CI check that requires a version bump when those paths change.🤖 Generated with Claude Code
Summary by CodeRabbit