releasing-a-version

Topics in the source

• Releasing a version

Each plugin under plugins/ / is versioned on its own, so each released plugin gets its own commit and its own tag. Every push to main ships to users at once (distribution is by commit SHA); the version and CHANGELOG record what shipped. 1. Pick plugins and bumps. For each plugin, read the ## [Unreleased] section of its CHANGELOG.md and the commits since its last tag (git tag --list ' -v', then git log ..HEAD -- plugins/ ). Release the plugins with unreleased changes, unless the user named others. The Unreleased bullets decide the semver bump: MAJOR for a breaking change to output, schema or CLI; MINOR for anything additive; PATCH for fixes, docs and refactors. 2. Run git status. The release commits should hold only the version bump, so if unrelated changes are present, ask the user how to handle them. Run each plugin's smoke test if it has one (find plugins/ -name smoketest.py). When the plugin has hooks/hooks.json (a mod), run claude plugin validate plugins/ and claude plugin test plugins/ . For every plugin you release, run the claude.ai directory checker, python3 tools/checkdirectoryrules.py release plugins/ --fail-on hold, and once its smoke test, python3 tools/smoketestdirecto

This is an excerpt. Refer to the complete source and its current requirements.