Versions
How BlixtFS releases are numbered and published, and how to tell which one you are running.
These docs describe BlixtFS 2.9, released on 24 September 2026.
Version numbers
BlixtFS uses semantic versioning: MAJOR.MINOR.PATCH.
- Major releases mark large changes to the product.
- Minor releases add features.
- Patch releases fix bugs.
Any release that needs action when you upgrade, such as a database change, says so in the upgrade guide.
Pre-release builds carry a suffix such as 2.10.0-rc1.
Image tags
Every release is published to Docker Hub under docker.io/blixtfs/. Each image
is tagged three ways:
| Tag | Example | Meaning |
|---|---|---|
| Version | blixtfs/standard:2.9.0 |
One specific release. Use this in production. |
| Build | blixtfs/standard:20260924.1 |
One specific build, by date and sequence number. |
latest |
blixtfs/standard:latest |
The most recent release, moved only after it has been verified. |
All images are multi-architecture (linux/amd64 and linux/arm64).
Pin a version tag in production and upgrade deliberately.
latestis convenient for trying BlixtFS out, but it changes under you.
Which version am I running?
Every BlixtFS server prints its edition and version when it starts:
docker logs blixt 2>&1 | grep "Blixt File System"
Blixt File System Standard edition version 2.9.0
In Kubernetes, check any pod’s log the same way, or look at the image tag:
kubectl -n bfs get deploy -o wide