release

Automate semantic versioning and changelog generation by analyzing commit history with commitizen to determine version bumps and git-cliff to create a comprehensive changelog. This ensures version numbers and release notes stay consistent across pyproject.toml or package.json and Git history.

Git-cliff works with both pyproject.toml and package.json for release versioning. The Skill manages version bumps directly within these configuration files, ensuring your semantic version updates align with your project's specific package manager and Git history.

The best way to create annotated Git tags and push releases automatically is by using a workflow that performs pre-flight checks, generates changelogs with git-cliff, creates the tag, and handles push confirmations to ensure commits and tags sync to the remote repository safely.

Determine the next semantic version by parsing commit history with commitizen, which intelligently identifies whether a major, minor, or patch bump is required based on your conventional commit messages and explicit flags.

Yes, you can run a dry-run for Git tagging and version bumping before pushing. The workflow handles dry-runs and pre-flight checks, allowing you to verify changelog generation and version updates without making permanent changes to the remote repository.

Using commitizen for automated version bumps prevents human error and ensures consistency, unlike manual tagging. It intelligently calculates the correct semantic version from your commit history and synchronizes updates across your changelog, configuration files, and Git tags.