You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stephanos Ioannidis edited this page Mar 24, 2026
·
5 revisions
Docker Image Versions
Versioning Rule
Zephyr Docker image uses the major.minor.revision version format:
major is always 0.
minor is incremented for every Zephyr release.
revision is incremented for every new Docker image release.
Each major.minor version, also called "compatibility level", is associated with a specific Zephyr release and hence a Zephyr release branch (vX.Y-branch).
For example, the Zephyr Docker image version 0.28.x is associated with Zephyr 4.2 release and the Zephyr v4.2-branch tracks the CI image v0.28.x.
When a new Zephyr version is released, the Zephyr Docker image release branch for the last major.minor release is created, and any updates for the corresponding Zephyr version are released from that release branch.
For example, at the time of Zephyr 4.2 release, a new Zephyr Docker image release branch, v0.28-branch, is created and any future Docker image updates for Zephyr 4.2 must be merged to and released from the v0.28-branch.