mm-release

Automating version bumping and changelog updates requires a tool that modifies package manifests and appends new release items to CHANGELOG.md. This skill handles both tasks automatically, applying SemVer rules to your manifests before updating the changelog with the latest version items.

Cutting a release with git tagging and pushing is best handled by automation scripts that manage the entire flow. This skill tags the commit with the new version and pushes the release to your repository, eliminating the need for manual git commands and reducing deployment errors.

Previewing a version bump and changelog changes is supported using a dry-run flag. You can run the release process with a preview mode to verify the version increment and changelog updates before any modifications are committed or pushed to the version control system.

Explicit version specification is fully supported alongside standard SemVer increments like patch, minor, and major. You can provide a specific version number in the X.Y.Z format to override the default semantic versioning logic for your software deployment.

Checking the current version of your project can be done by running the release command with a specific flag. This prints the current version from your package manifests without modifying any files, allowing you to verify the baseline before bumping.

Automated release automation should be used when your team needs a fast, reliable deployment process that reduces manual tasks. It is perfect for projects requiring consistent SemVer versioning, accurate changelog updates, and error-free git tagging without manual intervention.