semver-release

Automating semantic version releases across multiple ecosystems involves analyzing commit history to infer versions and updating discovered version files like package.json, pyproject.toml, Cargo.toml, and pubspec.yaml simultaneously.

Generating changelogs and updating version files from git commit history requires analyzing conventional or custom commit patterns to infer the new semantic version, then applying synchronized updates to your multilingual changelogs and version configurations.

Automated version bumping works with pyproject.toml and Cargo.toml by detecting common version files across ecosystems, ensuring synchronized updates are applied to all discovered configurations during the release workflow.

To start an automated release workflow, your git repository must have a clean working tree, discovered version files, and existing changelogs, ensuring a stable base for creating annotated git commits and tags.

You can preview and override an inferred semantic version before creating a git tag, as the automated release workflow supports interactive previews and user overrides to ensure the correct version is committed.

You should not use automated semantic versioning when your git repository has a dirty working tree or lacks existing changelogs and discoverable version files, as these are required prerequisites for the release automation to function correctly.