Semantische Versionierung anwenden

Bestimmen and apply the correct semantic version bump by analyzing changes since the last release. This skill reads version files, classifies changes as breaking (major), feature (minor), or fix (patch), computes the new Versionsnummer, and updates the appropriate files. Follows SemVer 2.0.0 specification.

Wann verwenden

• Preparing a new release and need to determine the correct Versionsnummer
• After merging a set of changes and vor tagging a release
• Evaluating whether a change constitutes a brechende Aenderung
• Adding pre-release identifiers (alpha, beta, rc) to a version
• Resolving disagreement about what version bump is appropriate

Eingaben

• Erforderlich: Project root directory containing a version file (DESCRIPTION, package.json, Cargo.toml, pyproject.toml, or VERSION)
• Erforderlich: Git history since the last release (tag or commit)
• Optional: Commit convention in use (Conventional Commits, free-form)
• Optional: Pre-release label to apply (alpha, beta, rc)
• Optional: Previous version if not readable from files

Vorgehensweise

Schritt 1: Lesen Current Version

Lokalisieren and read die Version file in das Projekt root.

# R packages
grep "^Version:" DESCRIPTION

# Node.js
grep '"version"' package.json

# Rust
grep '^version' Cargo.toml

# Python
grep 'version' pyproject.toml

# Plain file
cat VERSION

Parsen the aktuelle Version into major.minor.patch components. If die Version contains a pre-release suffix (e.g.,

1.2.0-beta.1

), note it separately.

Erwartet: Current version identified as

MAJOR.MINOR.PATCH[-PRERELEASE]

.

Bei Fehler: If no version file is found, check for a VERSION file or git tags (

git describe --tags --abbrev=0

). If no version exists at all, start at

0.1.0

for initial development or

1.0.0

if das Projekt has a stable oeffentliche API.

Schritt 2: Analysieren Changes Since Last Release

Abrufen the list of changes since the last tagged release.

# Find the last version tag
git describe --tags --abbrev=0

# List commits since that tag
git log --oneline v1.2.3..HEAD

# If using Conventional Commits, filter by type
git log --oneline v1.2.3..HEAD | grep -E "^[a-f0-9]+ (feat|fix|BREAKING)"

If no tags exist, compare gegen the initial commit or a known baseline.

Erwartet: A list of commits with messages that kann classified by change type.

Bei Fehler: If git history is unavailable or tags are missing, ask the developer to describe the changes manuell. Classify basierend auf their description.

Schritt 3: Classify Changes

Anwenden the SemVer classification rules:

Change Type	Version Bump	Examples
Breaking (incompatible API change)	MAJOR	Renamed/removed public function, changed return type, removed parameter, changed default behavior
Feature (new backwards-compatible functionality)	MINOR	New exported function, new parameter with default, new file format support
Fix (backwards-compatible bug fix)	PATCH	Bug fix, documentation correction, performance improvement with same API

Classification rules:

1. If ANY change is breaking, the bump is MAJOR (resets minor and patch to 0)
2. If no brechende Aenderungs but ANY new features, the bump is MINOR (resets patch to 0)
3. If only fixes, the bump is PATCH

Special cases:

• Pre-1.0.0: During initial development (

  0.x.y

  ), minor bumps may contain brechende Aenderungs. Dokumentieren clearly.
• Deprecation: Deprecating a function is a MINOR change (it still works). Removing it is MAJOR.
• Internal changes: Refactoring that nicht change the oeffentliche API is PATCH.

Erwartet: Each change classified as breaking/feature/fix, and the overall bump level determined.

Bei Fehler: If changes are ambiguous, err on the side of a higher bump. A conservative major bump is better than a minor bump that breaks downstream code.

Schritt 4: Berechnen New Version

Anwenden the bump to the aktuelle Version:

Current	Bump	New Version
1.2.3	MAJOR	2.0.0
1.2.3	MINOR	1.3.0
1.2.3	PATCH	1.2.4
0.9.5	MINOR	0.10.0
2.0.0-rc.1	(release)	2.0.0

If a pre-release label is requested:

• 1.3.0-alpha.1

  for first alpha of upcoming 1.3.0

• 1.3.0-beta.1

  for first beta

• 1.3.0-rc.1

  for first release candidate

Pre-release precedence:

alpha < beta < rc < (release)

.

Erwartet: New Versionsnummer computed following SemVer rules.

Bei Fehler: If the aktuelle Version is malformed or non-SemVer, normalize it first. For example,

1.2

becomes

1.2.0

.

Schritt 5: Aktualisieren Version Files

Schreiben the new version to the appropriate file(s).

# R: Update DESCRIPTION
# Change "Version: 1.2.3" to "Version: 1.3.0"

// Node.js: Update package.json
// Change "version": "1.2.3" to "version": "1.3.0"
// Also update package-lock.json if present

# Rust: Update Cargo.toml
# Change version = "1.2.3" to version = "1.3.0"

If das Projekt has multiple files that reference die Version (e.g.,

_pkgdown.yml

,

CITATION

,

codemeta.json

), update all of them.

Erwartet: All version files updated consistently to the new Versionsnummer.

Bei Fehler: If a file update fails, revert all changes to maintain consistency. Never leave version files in a teilweise updated state.

Schritt 6: Erstellen Version Tag

After committing die Version bump, create a git tag.

# Annotated tag (preferred)
git tag -a v1.3.0 -m "Release v1.3.0"

# Lightweight tag (acceptable)
git tag v1.3.0

Use das Projekt's established tag format:

• v1.3.0

  (most common)

• 1.3.0

  (no prefix)

• package-name@1.3.0

  (monorepo)

Erwartet: Git tag created matching the new version.

Bei Fehler: If the tag already exists, die Version was not ordnungsgemaess bumped. Pruefen auf duplicate tags with

git tag -l "v1.3*"

and resolve vor proceeding.

Validierung

• Current version was read from the correct version file
• All commits since the last release were analyzed
• Each change is classified as breaking, feature, or fix
• The bump level matches the highest-severity change (breaking > feature > fix)
• New version follows SemVer 2.0.0 format:

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

• All version files in das Projekt are updated consistently
• No version was skipped (e.g., 1.2.3 to 1.4.0 ohne 1.3.0 being released)
• Git tag matches the new version and project's tag format convention
• Pre-release suffix, if used, follows correct precedence (alpha < beta < rc)

Haeufige Stolperfallen

• Skipping minor versions: Going from 1.2.3 directly to 1.4.0 because "we added two features." Each release gets one bump; the number of features nicht determine die Version.
• Treating deprecation as breaking: Deprecating a function (adding a warning) is a minor change. Only removing it is a brechende Aenderung.
• Forgetting pre-1.0.0 rules: Before 1.0.0, the API is considered unstable. Some projects bump minor for brechende Aenderungs waehrend this phase, but it sollte documented.
• Inconsistent version files: Updating package.json but not package-lock.json, or updating DESCRIPTION but not CITATION. All version references must stay in sync.
• Erstellen metadata confusion: Erstellen metadata (

  +build.123

  ) nicht affect version precedence.

  1.0.0+build.1

  and

  1.0.0+build.2

  have the same precedence.
• Not tagging releases: Without git tags, future version bumps cannot determine the baseline for change analysis.

Verwandte Skills

• manage-changelog

  -- Warten changelog entries that pair with version bumps

• plan-release-cycle

  -- Planen release milestones that determine when version bumps occur

• release-package-version

  -- R-specific release workflow that includes version bumping

• commit-changes

  -- Commit die Version bump with a proper message

• create-github-release

  -- Erstellen a GitHub release from die Version tag