[PR #108] [MERGED] fix(plugin): let Claude Code track commits instead of a pinned 0.2.0 #130

New issue

Closed

opened 2026-10-15 20:53:39 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 20:53:39 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/rehan-remade/universal-modder/pull/108
Author: @AltDoug
Created: 10/6/2026
Status: ✅ Merged
Merged: 10/6/2026
Merged by: @rehan-remade

Base: main ← Head: fix/claude-plugin-track-commits

📝 Commits (1)

bb29860 fix(plugin): let Claude Code track commits instead of a pinned 0.2.0

📊 Changes

1 file changed (+0 additions, -1 deletions)

View changed files

📝 .claude-plugin/plugin.json (+0 -1)

📄 Description

Claude Code decides whether a plugin needs an update by comparing a version string, and .claude-plugin/plugin.json pins it to "version": "0.2.0". That string hasn't changed since v0.2, so nothing merged after it ever reaches people who installed through /plugin. claude plugin update says universal-modder is already at the latest version (0.2.0)., and marketplace auto-update skips it for the same reason. To pick up #94-#101 I had to uninstall and reinstall.

The Claude Code docs cover this case (https://code.claude.com/docs/en/plugins/loading, "Versions and updates"): a pinned version "keeps every user on the cached copy until its author changes the string, however many commits they push", and "to let users track commits instead, leave version out of both the manifest and the entry". The marketplace entry already has no version, so this PR only removes the line from .claude-plugin/plugin.json. The Codex, Cursor, Gemini and pyproject versions are untouched, and so is um --version.

Checked on Windows 11 by installing each ref into a clean CLAUDE_CONFIG_DIR:

this branch: installed_plugins.json records "version": "bb298605e9b5" (the commit), so every new commit on main counts as an update;
main: "version": "0.2.0".

claude plugin validate . passes; its one warning (root CLAUDE.md isn't loaded as plugin context) is already there on main.

If you'd rather keep semver releases, the alternative is to bump version on every release. Without one of the two, users never get updates.

Found and fixed with AI assistance (Claude Code); the install check was run on Windows 11.

🤖 Generated with Claude Code

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/rehan-remade/universal-modder/pull/108 **Author:** [@AltDoug](https://github.com/AltDoug) **Created:** 10/6/2026 **Status:** ✅ Merged **Merged:** 10/6/2026 **Merged by:** [@rehan-remade](https://github.com/rehan-remade) **Base:** `main` ← **Head:** `fix/claude-plugin-track-commits` --- ### 📝 Commits (1) - [`bb29860`](https://github.com/rehan-remade/universal-modder/commit/bb298605e9b555aa6706bb5be4945e108cb0e24d) fix(plugin): let Claude Code track commits instead of a pinned 0.2.0 ### 📊 Changes **1 file changed** (+0 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.claude-plugin/plugin.json` (+0 -1) </details> ### 📄 Description Claude Code decides whether a plugin needs an update by comparing a version string, and `.claude-plugin/plugin.json` pins it to `"version": "0.2.0"`. That string hasn't changed since v0.2, so nothing merged after it ever reaches people who installed through `/plugin`. `claude plugin update` says `universal-modder is already at the latest version (0.2.0).`, and marketplace auto-update skips it for the same reason. To pick up #94-#101 I had to uninstall and reinstall. The Claude Code docs cover this case (https://code.claude.com/docs/en/plugins/loading, "Versions and updates"): a pinned version "keeps every user on the cached copy until its author changes the string, however many commits they push", and "to let users track commits instead, leave `version` out of both the manifest and the entry". The marketplace entry already has no version, so this PR only removes the line from `.claude-plugin/plugin.json`. The Codex, Cursor, Gemini and pyproject versions are untouched, and so is `um --version`. Checked on Windows 11 by installing each ref into a clean `CLAUDE_CONFIG_DIR`: - this branch: `installed_plugins.json` records `"version": "bb298605e9b5"` (the commit), so every new commit on main counts as an update; - main: `"version": "0.2.0"`. `claude plugin validate .` passes; its one warning (root `CLAUDE.md` isn't loaded as plugin context) is already there on main. If you'd rather keep semver releases, the alternative is to bump `version` on every release. Without one of the two, users never get updates. Found and fixed with AI assistance (Claude Code); the install check was run on Windows 11. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-15 20:53:39 +00:00