payload-plugin-release
Automates the release workflow for the Payload Newsletter Plugin. Use when releasing a new version, bumping the version, or publishing to npm.
When & Why to Use This Skill
This Claude skill automates the end-to-end release workflow for the Payload Newsletter Plugin. It streamlines version management, changelog updates, and npm publishing by integrating with GitHub Actions, ensuring consistent, error-free software deployments and adherence to semantic versioning.
Use Cases
- Automated Version Bumping: Seamlessly increment patch, minor, or major versions in package.json following semantic versioning rules.
- Changelog Management: Automatically generate and format standardized changelog entries to maintain a transparent project history.
- CI/CD Pipeline Integration: Trigger GitHub Actions for automated testing, building, and npm publishing by pushing commits to the main branch.
- Pre-release Validation: Execute automated typechecks (e.g., via Bun) before committing changes to prevent broken code from reaching production.
| name | payload-plugin-release |
|---|---|
| description | Automates the release workflow for the Payload Newsletter Plugin. Use when releasing a new version, bumping the version, or publishing to npm. |
Execute the automated release workflow for the Payload Newsletter Plugin, ensuring proper versioning, changelog updates, and triggering GitHub Actions for npm publishing.
- NEVER create git tags manually - GitHub Actions handles tag creation
- ALWAYS check the current date before updating changelog
- ALWAYS run typecheck before committing release changes
- Version bumps follow semantic versioning (major.minor.patch)
What type of release?
- Patch (bug fixes) - e.g., 0.25.11 → 0.25.12
- Minor (new features, backward compatible) - e.g., 0.25.11 → 0.26.0
- Major (breaking changes) - e.g., 0.25.11 → 1.0.0
Also provide: What changes are being released? (for changelog)
Run typecheck to ensure no TypeScript errors: ```bash bun typecheck ``` If errors exist, fix them before proceeding. Check current version: ```bash grep '"version"' package.json | head -1 ``` Get current date for changelog: ```bash date +"%Y-%m-%d" ``` Update version in package.json based on release type: - Patch: increment last number (0.25.11 → 0.25.12) - Minor: increment middle, reset last (0.25.11 → 0.26.0) - Major: increment first, reset others (0.25.11 → 1.0.0) Add entry at TOP of CHANGELOG.md:## [NEW_VERSION] - YYYY-MM-DD
### Fixed/Added/Changed
- Description of changes
Categories to use:
- Added - new features
- Changed - changes in existing functionality
- Fixed - bug fixes
- Removed - removed features
- Security - security fixes
GitHub Actions will automatically:
- Detect the new version
- Run tests and type checking
- Build the project
- Create the git tag
- Publish to npm
- Create a GitHub release