Version Numbering

Overview

Bloomreach Content follows the Semantic Versioning Scheme for all product releases.

This approach enables Bloomreach to deliver new features through multiple minor releases each year, while maintaining backward compatibility. You can remain on a major version if you choose not to upgrade immediately to a new major release.

Semantic Versioning Explained

Semantic versioning uses a three-part version number in the format:

MAJOR.MINOR.PATCH

For example:

14.1.2

Each segment has a specific meaning:

• MAJOR: Incremented for releases that introduce new functionality or architectural changes that may break backward compatibility or introduce incompatible API changes. Major releases are typically issued once per year.
• MINOR: Incremented for releases that add new functionality in a backward-compatible manner. Minor releases occur several times per year.
• PATCH: Incremented for releases that address bug fixes or minor changes, always maintaining backward compatibility with the current major version. Patch releases are typically issued every 1–2 months.

Info: Starting with version 16.6.0, Bloomreach introduced a new Incubating Features and Extension Points Policy. This policy may affect backward compatibility for minor versions. For details, see the Incubating Features Policy.

In many cases, the patch version is omitted in discussions or documentation. For example, "brXM version 14.1" refers to the latest patch release in the 14.1 series, such as 14.1.5 if that is the most recent.

Artifact Version Numbers

Bloomreach Content consists of multiple internal artifacts. All artifact version numbers match the corresponding Bloomreach Content release version.

Maintenance (patch) versions are always backward compatible. Minor versions may introduce changes that are not backward compatible. Review the release notes for each version to understand upgrade requirements and API changes.