Semantic Versioning

Automate version management and changelog generation following SemVer principles.

Follow the target repository’s release workflow and protected-branch rules before any commit/tag/publish. These configurations are alternatives, not permission to bypass a PR-only branch. A version bump does not authorize registry or GitHub publication. Derive breaking changes from public API compatibility, not commit type alone; refactor/docs release rules are configurable. Version scripts below support only plain numeric MAJOR.MINOR.PATCH and simple metadata files; use a SemVer-aware library for prereleases/builds and verify exact file changes before committing. Do not delete or move published tags to resolve duplicates.

Prerequisites

• Git repository with commit history
• Node.js (for most tools)
• Conventional commits (recommended)

Semantic Versioning Basics

Version Format

MAJOR.MINOR.PATCH[-PRERELEASE][+BUILD]