Versioning
This page introduces the release cycle and versioning approach used in Aidbox development
Last updated
Was this helpful?
This page introduces the release cycle and versioning approach used in Aidbox development
Last updated
Was this helpful?
Aidbox docker images are available on .
Starting from October 2024 Aidbox follows a MAJOR.MINOR version scheme:
MAJOR version: Formatted as YYMM (e.g., 2409 for September 2024)
MINOR version: An increasing number starting from zero
Each update increments the MINOR version. For example:
New release: 2409.0
Bugfix: 2409.1
Bugfix 2: 2409.2
New release: 2410.0
Bugfix for 2409: 2409.3
Bugfix for 2410: 2410.1
Images built for full versions (MAJOR.MINOR) remain unchanged. You can specify the full version instead of the Docker manifest SHA to use a specific build.
Aidbox provides several release channels, each updated with changes and new builds:
The most recent Aidbox build. We highly recommend using the edge channel in staging and dev environments to get access to new functionality and detect potential issues as soon as possible. Every commit into the Aidbox code base after successful CI is published to the edge channel. The edge channel may have issues and/or regressions.
The latest channel is identical to the last minor version of the last release.
Latest releases contain new functionality, bugfixes, and optimizations and passed all available QA and review processes by the Health Samurai team. If you're actively developing we recommend using latest. These releases are updated monthly.
The stable channel is identical to the last minor version of the previous release.
Stable releases are ready for production. The current stable is the previous latest release. These releases are updated monthly.
This channel contains the last changes to the MAJOR release, which are undergoing internal QA processes. After these processes are finished, a new full version is released.
For every release, a tag in the format YYMM (e.g., 2409 for September 2024) is created to allow users to check out a specific Aidbox version. This tag is automatically updated with each minor version and corresponds to the last minor version for the major version.
By using these channels and understanding the version numbering system, you can choose the most appropriate Aidbox build for your development, staging, and production environments.
Starting in January 2022 we are introducing long-term support releases. The Aidbox team will backport security and critical bug fixes to LTS releases throughout a two-year support window.
Aidbox LTS releases are scheduled to be published twice a year. If you are not interested in getting new features on a monthly basis but want to get critical bug fixes, please consider switching to LTS releases.
✔
2024-10
2026-10
✔
2024-04
2026-04
✔
2023-08
2025-08
✔
2023-04
2025-04
—
2022-08
2023-08
—
2022-04
2023-04
2024-10-18
Fixed critical security issues
2024-10-03
Fixed critical vulnerabilities
2024-09-25
Fixed critical vulnerabilities
2024-09-18
Fixed critical vulnerabilities
2024-09-06
Fixed critical vulnerabilities
2024-01-18
Fixed recursion in transaction bundles. Fixed missing search modifier.
2024-01-16
Supported JWT without kid signature check
2023-11-01
Updated dependencies
2023-09-11
Updated dependencies
2023-07-12
Fixed security issue
2023-06-29
Fixed critical vulnerabilities
2023-06-07
Fixed security issue
2023-05-29
Fixed critical vulnerabilities
2023-04-28
Fixed security issue
2023-04-05
Fixed critical vulnerabilities
2023-02-03
Fixed critical vulnerabilities
2022-11-03
Fixed security issues in Search API.
2022-10-10
Fixed critical issue on subscriptions in DB transaction that can break DB connection.
, ,
, ,
,
,
,
,
,
,
,
,
,