chore: version bump rule + hookify 0.2.1, metacognitive-guard 0.4.1#136
chore: version bump rule + hookify 0.2.1, metacognitive-guard 0.4.1#136
Conversation
…acognitive-guard 0.4.1 Plugin cache is version-keyed — without bumps, new sessions serve stale code. Added mandatory rule to CLAUDE.md so this never happens again. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (3)
✨ 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 |
Summary of ChangesHello @ANcpLua, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces a mandatory version bump rule for plugins to avoid cache inconsistencies and updates the versions of the Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a mandatory version bump rule in CLAUDE.md for plugin code changes and applies this rule by bumping the versions for the hookify and metacognitive-guard plugins. The changes are well-justified by recent fixes mentioned in the changelog. My review includes one suggestion to improve the new documentation by making the list of plugin components that require a version bump more complete.
|
|
||
| ### ⚠️ PLUGIN VERSION BUMP - DO NOT SKIP | ||
|
|
||
| **When you modify a plugin's code (hooks, commands, skills, agents), you MUST bump its version:** |
There was a problem hiding this comment.
The list of plugin code components that trigger a mandatory version bump is incomplete. It's missing scripts. According to docs/PLUGINS.md, scripts can be part of a plugin. Modifying a script that is part of a plugin's functionality should also require a version bump to avoid serving stale code from the cache.
| **When you modify a plugin's code (hooks, commands, skills, agents), you MUST bump its version:** | |
| **When you modify a plugin's code (hooks, commands, skills, agents, scripts), you MUST bump its version:** |
There was a problem hiding this comment.
Pull request overview
Updates internal repo guidance and plugin manifests to ensure plugin changes are picked up by new Claude sessions (cache is version-keyed), alongside patch version bumps for two plugins.
Changes:
- Added a mandatory “plugin version bump” rule to
CLAUDE.md. - Bumped
hookifyversion0.2.0 → 0.2.1. - Bumped
metacognitive-guardversion0.4.0 → 0.4.1.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
CLAUDE.md |
Adds a rule requiring version bumps when plugin code changes to avoid stale cached plugin loads. |
plugins/hookify/.claude-plugin/plugin.json |
Patch version bump for hookify. |
plugins/metacognitive-guard/.claude-plugin/plugin.json |
Patch version bump for metacognitive-guard. |
| { | ||
| "name": "metacognitive-guard", | ||
| "description": "Cognitive amplification stack: epistemic hooks, competitive review, commit integrity checks, CI verification scripts, and deep-thinking agents.", | ||
| "version": "0.4.0", | ||
| "version": "0.4.1", | ||
| "author": { |
There was a problem hiding this comment.
The marketplace manifest still lists metacognitive-guard as version 0.4.0. After bumping the plugin's plugin.json to 0.4.1, please also update .claude-plugin/marketplace.json so the declared marketplace version stays in sync with the plugin manifest (and to avoid users/install flows seeing the old version).
| { | ||
| "name": "hookify", | ||
| "version": "0.2.0", | ||
| "version": "0.2.1", | ||
| "description": "Create hooks to prevent unwanted behaviors. Fork with global rules support ($HOME/.claude/global-rules/)", |
There was a problem hiding this comment.
The marketplace manifest still lists hookify as version 0.2.0. Since this PR bumps hookify's plugin.json to 0.2.1, please update .claude-plugin/marketplace.json accordingly to keep marketplace metadata consistent with the plugin manifest.
| **When you modify a plugin's code (hooks, commands, skills, agents), you MUST bump its version:** | ||
|
|
||
| 1. Open `plugins/<name>/.claude-plugin/plugin.json` | ||
| 2. Increment the `version` field (patch for fixes, minor for features) | ||
| 3. The plugin cache (`~/.claude/plugins/cache/`) is version-keyed — without a bump, new sessions won't pick up changes | ||
|
|
||
| **NO EXCEPTIONS.** Changed plugin code without version bump = users stuck on stale cache. |
There was a problem hiding this comment.
This new rule instructs bumping plugins/<name>/.claude-plugin/plugin.json, but the repo also declares per-plugin versions in .claude-plugin/marketplace.json (and it currently still references the old versions for these plugins). Consider extending this section to require updating the marketplace manifest version entry too (or referencing tooling/scripts/sync-marketplace.sh), otherwise version bumps can remain partially applied.
| **When you modify a plugin's code (hooks, commands, skills, agents), you MUST bump its version:** | |
| 1. Open `plugins/<name>/.claude-plugin/plugin.json` | |
| 2. Increment the `version` field (patch for fixes, minor for features) | |
| 3. The plugin cache (`~/.claude/plugins/cache/`) is version-keyed — without a bump, new sessions won't pick up changes | |
| **NO EXCEPTIONS.** Changed plugin code without version bump = users stuck on stale cache. | |
| **When you modify a plugin's code (hooks, commands, skills, agents), you MUST bump its version _everywhere it is declared_:** | |
| 1. Open `plugins/<name>/.claude-plugin/plugin.json`. | |
| 2. Increment the `version` field (patch for fixes, minor for features). | |
| 3. Update the matching plugin entry in `.claude-plugin/marketplace.json` so its `version` matches the plugin's `plugin.json` **OR** run `./tooling/scripts/sync-marketplace.sh` to auto-sync versions. | |
| 4. Remember: the plugin cache (`~/.claude/plugins/cache/`) is version-keyed — without a bump (and a synced marketplace entry), new sessions won't pick up changes. | |
| **NO EXCEPTIONS.** Changed plugin code without a complete version bump (manifest **and** marketplace) = users stuck on stale cache or inconsistent versions. |
Summary
Test plan
🤖 Generated with Claude Code