Versioning

FiveNet uses CalVer versioning. That means the version number is based on the release date instead of a traditional semantic version like 1.2.3.

You will usually see one of these two formats:

• Release version: v2026.3.1
• Development version: v2026.3.1-55-g07bf5c8e5

Release Version

A full release version looks like this:

v2026.3.1

This format is:

vYYYY.M.P

• YYYY = release year
• M = release month
• P = patch or revision number for that month

In the example v2026.3.1:

• 2026 means the year 2026
• 3 means March
• 1 means the first release published for that month

Development Version

A development version looks like this:

v2026.3.1-55-g07bf5c8e5

This is based on the same release version, but with extra Git metadata appended:

vYYYY.M.P-COMMITS-gHASH

• v2026.3.1 = the nearest release tag the build is based on
• 55 = the build contains 55 commits after that tag
• g07bf5c8e5 = the short Git commit hash of the exact source revision

In practice, this means the build was created from code that is newer than the v2026.3.1 release, but not yet published as the next full release tag.

Does "Dev" Mean Unstable?

Not necessarily.

A development version simply means the build was created from a commit between tagged releases. It does not automatically mean the build is broken, unsafe, or unsuitable for production.

The main difference is version labeling:

• A release version is a tagged, full release.
• A development version is a build from a specific Git commit after the last tagged release.

Because the commit hash is included, development versions are often even easier to trace back to the exact source code that was used.

Quick Examples

• v2026.3.1 The first tagged release from March 2026.
• v2026.3.1-55-g07bf5c8e5 A build from 55 commits after v2026.3.1, based on commit 07bf5c8e5.

Summary

If you only remember one thing, it is this:

How to Check Your Version

# Assumes you are in the directory containing your docker-compose.yml / docker-compose.yaml file
docker compose exec fivenet fivenet --version

# Assumes that Helm was used to deploy FiveNet and kubectl is connected to your cluster and FiveNet app namespace
kubectl exec deployment/fivenet -- fivenet --version
# Additionally check the image.tag used in your Helm values to see the version of the image you are currentlyrunning

# Assumes that the fivenet binary is in your PATH
fivenet --version

# Assumes that the fivenet.exe is in your PATH
fivenet.exe --version