🚀 VoxBox 10.0.0 is here — with a brand-new container tag scheme! Starting with VoxBox 10.0.0, the VoxBox container follows its own semantic versioning, independent of the OpenVox version included in the image. The new tags clearly identify both components: 📌

10.0.0-openvox8.28.1

An immutable release pinned to an exact VoxBox and OpenVox version. 📌

10.0.0-openvox8

An immutable VoxBox release for the OpenVox 8 flavor. (it's shorter to write 😄) We have also clarified the moving and development tags: •

latest

points to the highest successfully published VoxBox SemVer release. It does not simply follow the most recently built image. ◦ Publishing or rebuilding an older release or backport will not move

latest

backwards. For example, if

10.2.0

is the highest published release, a later build of

10.1.5

will not replace it. •

main

follows the latest build from the main branch. •

sha-<git-sha>

identifies an immutable build from a specific Git revision. For reproducible CI pipelines, we recommend pinning either a versioned release tag or a

sha-*

tag:

podman pull <http://ghcr.io/voxpupuli/voxbox:10.0.0-openvox8.28.1|ghcr.io/voxpupuli/voxbox:10.0.0-openvox8.28.1>

⚠️ Existing legacy tags such as

8

,

8-latest

, and

8.28.1-latest

remain available, but they will no longer be updated. Bare numeric tags such as

10

will not be published. The new scheme is available from both GHCR and Docker Hub. 🎉 github.com/voxpupuli/container-voxbox/…/v10.0.0 github.com/voxpupuli/container-voxbox#…