microsoft / microsoft/win-dev-skills

[Bug]: `.claude-plugin` / `.codex-plugin` manifest version has been `0.3.0` since v0.3.1, so plugin updates are not working

Open
#170 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
444
Forks
33
Avg merge
2h 59m
Merged PRs (30d)
11

Description

Describe the bug

The two client manifests never got bumped after v0.3.1, while marketplace.json tracked every release:

tag .claude-plugin/plugin.json .codex-plugin/plugin.json marketplace.json
v0.3.1 0.3.0 0.3.0 0.3.1
v0.4.0 0.3.0 0.3.0 0.4.0
v0.5.0 0.3.0 0.3.0 0.5.0
v0.6.0 0.3.0 0.3.0 0.6.0

At v0.6.0 the new agent-plugin/plugin.json correctly says 0.6.0, so it is only the two client manifests.

On Claude Code this means:

  • the payload installs to ~/.claude/plugins/cache/win-dev-skills/winui/**0.3.0** no matter which release it is;
  • claude plugin update winui@win-dev-skills compares manifest versions, decides it is already current, and never re-extracts;
  • claude plugin list reports Version: 0.3.0 for a 0.6.0 payload.

The practical effect is that no label anywhere tells you which payload is actually installed, and updating requires uninstall + install instead of update.

Suggested fix: bump the two client manifests as part of the release, and add a consistency check across all four manifests.

Affected skill / tool

area: plugin / install

To Reproduce

claude plugin marketplace add microsoft/win-dev-skills
claude plugin install winui@win-dev-skills
claude plugin list

Expected behavior

The two client manifests carry the version of the release they ship in

Session report (strongly recommended)

Build / runtime output

Copilot CLI version

No response

Plugin version

No response

OS version

No response

.NET SDK version

No response

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Inspect .claude-plugin/plugin.json, .codex-plugin/plugin.json, agent-plugin/plugin.json, and marketplace.json, comparing how release versions are represented. Update the two client manifests with the shipped release version, add a consistency check across all four manifests, and verify the result with the provided Claude plugin install and list commands.

Written by the indexing model from the issue text.

Assessment

Domain
release, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
76/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.