claude-code-plugin-release

Automating npm publish and GitHub releases requires coordinating version bumps across all manifests, validating builds, and pushing tags. This workflow handles committing changes, publishing packages, creating releases, and regenerating changelogs automatically.

Keeping version strings synchronized across multiple plugin manifests requires strict coverage verification during the release process. The workflow updates version numbers in all required npm and marketplace metadata files to ensure npx resolution remains consistent.

Generating changelogs and tagging releases for npm packages involves creating git tags, pushing commits, and regenerating changelog entries. This workflow automates the entire sequence, followed by a Discord notification for post-release visibility.

Yes, automating plugin version bumps and publishing requires git, gh, npm, and node installed in your environment. These dependencies are necessary for executing build verification, git tagging, npm publishing, and GitHub release creation.

Yes, this release workflow supports patch, minor, and major semantic versioning updates. You can request a specific version bump and the workflow will apply the correct semver increment across all required manifest and package files.

Local marketplace build artifacts become out of sync when version bumps are applied without regenerating synced outputs. Running the build-and-sync flow after updating manifests ensures the local marketplace and worker state matches the released distribution.