Merge pull request #4 from oposs/fix/commit-plugin-json

Commit plugin.json (0.2.0) — missed by PR #3 merge

Author: oetiker

.claude-plugin/plugin.json

@@ -0,0 +1,8 @@
+{
+"name": "cmk-oposs-plugin",
+"description": "A plugin for people developing checkmk plugins",
+"version": "0.2.0",
+"author": {
+  "name": "Tobias Oetiker <tobi@oetiker.ch>"
+}
+}

.gitignore

@@ -8,6 +8,7 @@
 !/.mkp-builder.ini.example
 !/.clinerules
 !/skills
+!/.claude-plugin
 *~
 *.swp
 *.bak

CHANGES.md

@@ -22,6 +22,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   `actions/checkout` v4→v7, `actions/upload-artifact` v4→v7,
   `actions/download-artifact` v4→v8, `softprops/action-gh-release` v2→v3
   (`oposs/mkp-builder` stays `@v2`).
+- Commit `.claude-plugin/plugin.json` (previously gitignored) so the plugin owns its
+  own version as the single source of truth (`0.2.0`); the marketplace entry no longer
+  carries a `version`. See `RELEASING.md` for the plugin release process.
 
 ### Fixed
 

RELEASING.md

@@ -0,0 +1,31 @@
+# Releasing
+
+This repo ships two things with **independent** version streams:
+
+## 1. The `mkp-builder` GitHub Action
+
+Versioned by git tags (`v2.2.0`, …) with a moving major tag (`@v2`). Cut a release by
+running the **Release** workflow (`workflow_dispatch`, bugfix/feature/major). It rolls
+`CHANGES.md`, tags, and moves `@v2`. Consumers pin `oposs/mkp-builder@v2`.
+
+## 2. The `cmk-oposs-plugin` Claude Code plugin
+
+The plugin's version lives **only** in `.claude-plugin/plugin.json` (`version`). It is the
+single source of truth — Claude Code resolves a plugin's version as
+`plugin.json → marketplace entry → commit SHA`, and `plugin.json` wins. The marketplace
+entry in [`oposs/claude-plugins`](https://github.com/oposs/claude-plugins) therefore carries
+**no** `version` field for this plugin (avoid setting it in two places — a stale duplicate
+silently masks the real one).
+
+### Releasing a plugin change
+
+1. Make the plugin/skill change under `skills/`.
+2. **Bump `version` in `.claude-plugin/plugin.json`** in the same change. Pushing new commits
+   without bumping does nothing — Claude caches the resolved version and keeps the old copy.
+3. Push to `main`.
+4. **Push a change to the marketplace repo** (`oposs/claude-plugins`) as well — Claude
+   re-resolves plugin versions when it re-fetches the marketplace, so the marketplace clone
+   has to move for the bump to be noticed. A one-line edit (e.g. a note in that repo) is
+   enough. *(This can be automated from CI later with a PAT that can push to the marketplace
+   repo; not wired up yet.)*
+5. Users run `/plugin marketplace update` then `/plugin update cmk-oposs-plugin`.