Question 1

How to set up HeadVer in a CI/CD pipeline?

Accepted Answer

Use the provided examples for Bash, PowerShell, or other languages to integrate HeadVer into your build scripts. Automate {yearweek} based on the current date and {build} via incremental counters in your CI server.

Question 2

HeadVer vs Semantic Versioning: which is better?

Accepted Answer

HeadVer is better for automating releases and tracking version age, but SemVer is superior for libraries needing clear patch/minor/major signals for dependency resolution. Choose based on your project's need for semantic meaning.

Question 3

Can HeadVer be used with Docker tags?

Accepted Answer

Yes, but Docker tags often use SemVer-like formats. You can map HeadVer's {head}.{yearweek}.{build} to tags, though ensure your registry supports the fixed-length format and consider using metadata for additional info.

Question 4

What happens when the yearweek rolls over after year 2100?

Accepted Answer

The README tips suggest updating the {head} number or using a 4-digit year for {yearweek}. This is a long-term edge case, but implementations should plan for it to avoid version collisions.

Question 5

How to handle prerelease versions in HeadVer?

Accepted Answer

HeadVer discourages -prerelease suffixes and recommends updating the {head} number instead. For beta testing, use separate build counters or metadata, but this may complicate workflow compared to SemVer's built-in support.

Question 6

Is HeadVer compatible with Git tags?

Accepted Answer

Yes, you can use HeadVer versions as Git tags, but ensure your tooling handles the fixed 4-digit {yearweek} and auto-incremented {build}. Scripts in the examples show how to generate and validate these tags.

HeadVer Spec

What is HeadVer Spec?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions