Release Management

What it does

This skill automates software release deployment and rollback processes specifically for sgcarstrends applications, ensuring stability and efficiency. It leverages semantic-release to manage versioning using a unified "v" prefix (e.g., v4.46.0), automatically updates CHANGELOG.md and package.json files across the monorepo, creates Git tags and GitHub Releases with auto-generated notes, and triggers Vercel deployments. Commits to the main branch trigger this automated release process.

When to use it

• When deploying new versions of sgcarstrends applications.
• To ensure consistent versioning across a monorepo project.
• For automating changelog generation and GitHub Release creation.
• To streamline the software release workflow, reducing manual effort.
• When needing to quickly view recent releases or check the status of a release workflow.

Key capabilities

• Automated semantic versioning (e.g., v4.46.0).
• Automatic CHANGELOG.md updates.
• Unified version management across a monorepo.
• GitHub Release creation with auto-generated notes.
• Vercel deployment triggered by release events.
• Uses conventional commits for version bump analysis.

Example prompts

• "Show me the last 5 releases."
• "What's the status of the release workflow?"
• "View the logs for the most recent release attempt."

Tips & gotchas

• Commit messages must adhere to the conventional commits format for version bumps to be calculated correctly. Refer to the conventional-commits skill for details.
• The release process is triggered by commits pushed to the main branch.
• Debugging failures involves checking GitHub Actions logs and verifying commit types and message formatting.