payload-plugin-release

<essential_principles>

• 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) </essential_principles>

1. Patch (bug fixes) - e.g., 0.25.11 → 0.25.12
2. Minor (new features, backward compatible) - e.g., 0.25.11 → 0.26.0
3. Major (breaking changes) - e.g., 0.25.11 → 1.0.0

Also provide: What changes are being released? (for changelog)

## [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:

1. Detect the new version
2. Run tests and type checking
3. Build the project
4. Create the git tag
5. Publish to npm
6. Create a GitHub release

<success_criteria>

• TypeScript passes with no errors
• Version bumped correctly in package.json
• CHANGELOG.md updated with correct date and version
• Changes committed and pushed to main
• User directed to GitHub Actions to monitor release </success_criteria>