vlad/reverse-skills-max
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
aecfc9365536c6f06d3590cf3c1321875c2426d3
reverse-skills-max/vendor-new/win-dev-skills/RELEASING.md

2.0 KiB
Raw Blame History

Releasing win-dev-skills

A plugin hosted here under plugins/<name>/ ships from main. A plugin maintained in another repo is released there, and the catalog then moves its pin to that release.

Release a plugin hosted here

In one PR, bump the plugin's version in its manifests and in its entries in the Copilot and Claude catalogs, bump the catalog version, and add a CHANGELOG.md section. Catalog check verifies that the versions match.

Move a pinned plugin to a new version

  1. Release the plugin in its source repo (for winui and winappcli: a microsoft/winappCli release). Note the release tag, its commit sha (gh api repos/<owner>/<repo>/commits/<tag> --jq .sha), and the plugin version.
  2. On a branch from main, update the plugin entry in all three catalogs:
    • .github/plugin/marketplace.json: source.ref, source.sha, version
    • .claude-plugin/marketplace.json: source.ref, source.sha, version
    • .agents/plugins/marketplace.json: source.ref, source.sha
  3. Bump the catalog version (metadata.version in the Copilot catalog and version in the Claude catalog) and add a ## [X.Y.Z] — YYYY-MM-DD section to CHANGELOG.md.
  4. Open a PR to main. Catalog check verifies the new pin resolves and the versions match.
  5. Merge. If the catalog version changed, auto-tag tags the merge commit vX.Y.Z.

Hosts pick up a plugin change when its version changes. Copilot and Codex also re-fetch when only the source changes; Claude Code keeps the installed copy until the version changes. So always ship new plugin content with a new plugin version.

Tags

release-post-merge.yml reads metadata.version from .github/plugin/marketplace.json on every push to main. If it changed, it tags the commit vX.Y.Z. It never moves an existing tag.

Tags up to v0.7.1 contain the winui plugin itself.

Rolling back

Ship a fixed version with a higher version number: for a pinned plugin, release it in the source repo and move the pin. Don't point the catalog back at an older version.