version-sdlc

You can automate semantic versioning and changelog generation by bumping the project version, creating an annotated git tag, optionally generating a CHANGELOG entry, and pushing the commit. This end-to-end release workflow relies on pre-computed version context to ensure safe, consistent semantic releases.

The best way to create an automated pre-release or hotfix workflow is to invoke the release process with dedicated flags like --pre or --hotfix. These trigger specific release scenarios that safely bump versions and apply git tags based on pre-computed context, while --auto mode skips interactive prompts for non-interactive runs.

To skip interactive prompts during an automated release and changelog bump, you use the --auto flag. This mode executes the end-to-end semantic versioning workflow non-interactively while still displaying the release plan for verification before performing git operations.

Yes, automated release management can work without pushing commits to the remote repository by applying the --no-push flag. This allows you to locally bump the semantic version, generate the changelog entry, and create the annotated git tag while preventing any remote repository updates.

Before executing git operations for a semantic release, pre-condition checks and error handling guardrails are enforced. These checks verify the required pre-computed version context and validate the environment to ensure safe releases across common Git workflows and project configurations.

Yes, you need pre-computed version context from skill/version.js to initialize automated semantic versioning and tagging. The --init flag triggers the setup process, consuming this specific context to safely perform version bumps and generate annotated git tags within your project.