Versioning and Tags

🚀Versioning and Tags

Advanced

Choose a supported version strategy and compatible release modifiers before creating a Git tag.

Commandcusty tag

📦Category

Versioning

🚀Quick Command

custy tag --strategy STRATEGY [OPTIONS]

---

SemVerPEP 440release modifiers

---

Overview

Custy's tag workflow can resolve versions through multiple strategies. Choose the strategy that matches the project's published version format.

---

Supported Strategies

📋Version Strategy Comparison

Property	Type	Description	Default	Required
semver	v1.2.3	Applications and libraries following Semantic Versioning.	-	No
pep440	1.2.3rc1	Python packages using PEP 440.	-	No
date	Date-derived	Calendar or date-oriented releases.	-	No
gitcount	Commit-count-derived	Build or internal sequencing.	-	No
commitizen	History-derived	Conventional Commit and Commitizen workflows.	-	No

---

Release Modifiers

Release modifiers include pre-release labels, post releases, development releases, metadata, and epochs. Compatibility depends on the selected strategy.

---

⚠️Do not mix incompatible formats

Choose a strategy first, then use only modifiers supported by that strategy. Inspect the resolved version during dry-run before creating a permanent tag.

---

Explicit Release Versions

An explicit --tag is the clearest override when the release version has already been approved. Confirm whether your project consistently uses a v prefix before entering it.