Release Pipeline
Release software correctly. Version bump, changelog, npm publish, GitHub release. One command, nothing forgotten. You’ve seen it happen. Someone bumps the version but forgets the changelog. Publishes to npm but skips the GitHub release. Tags the repo but never syncs the SKILL.md. Each step is simple. Remembering all of them every time is the hard part. Release Pipeline handles the full sequence. You run one command. It does everything else.What It Does
- Bumps the version (patch, minor, or major)
- Syncs SKILL.md with the new version
- Generates a changelog entry
- Commits and tags
- Publishes to npm and GitHub Packages
- Creates a GitHub release with your notes
Install
Usage
RELEASE-NOTES-v{version}.md file on your feature branch. Commit it with the code. The PR shows both the code and the notes together.
Quality Gates
Before anything publishes, the pipeline checks:- Release notes exist and come from a file (not a flag)
- Notes reference at least one GitHub issue
- Product docs are updated
- Technical docs are updated if source changed
- No stale merged branches hanging around
- Running from the main working tree (not a worktree)