codemie-release

Automated semantic versioning for npm CLI releases uses conventional commits to determine major, minor, or patch version bumps. It orchestrates git tagging, origin pushing, and GitHub release creation with generated notes in a repeatable workflow.

Automating GitHub release creation and git tagging involves a release orchestration workflow that reads conventional commits to generate release notes, bumps the package version, applies git tags, and pushes changes to the origin repository.

Yes, running an automated release requires a clean git working directory on the main branch. Preflight checks ensure the repository is in a clean state before performing version bumps and pushing git tags to origin.

Semantic versioning determines version bumps during an npm release by parsing conventional commit messages. Breaking changes trigger major bumps, new features trigger minor bumps, and fixes trigger patch bumps.

Yes, automated semantic releases integrate directly with the existing npm package.json version. The workflow reads the current version, calculates the next bump based on conventional commits, and updates the file before tagging.

Automated version bumping requires preflight checks to ensure a clean release state and prevent inconsistent tags. Verifying the main branch and working directory before pushing to git origin guarantees a repeatable, error-free release process.