Compatibility

This document outlines the compatibility between different versions of Mender components, such as the client and server.

Backward compatibility policy

Mender always provides an upgrade path from the past patch (e.g. 1.2.0 to 1.2.1) and minor version (e.g. 1.1.1 to 1.2.0), and releases follow Semantic Versioning. Note that according to Semantic Versioning, minor releases add new functionality (e.g from 1.2.0 to 1.3.0) so be sure to upgrade components to support the newer functionality before using it.

For example, when Mender releases a new Artifact format version, the new Mender Client still supports older versions of the Artifact format. However, the inverse is not true; the Mender Client does not support newer versions of the Artifact format. So in this case you need to upgrade all Mender clients before starting to use new versions of the Artifact format (and the features it enables).

As another example, the Mender Client supports one version of the server API, while the server can support several API versions. Therefore, always update the server before the client.

Mender also follows different support durations for different minor versions with LTS releases. Please refer to the Release-information for more information about LTS releases and the release schedule.

Specific versioning criteria

Since Semantic Versioning was primarily written for libraries, it is not necessarily clear what constitutes an API in the context of Mender. Below are the lists of specific criteria we use for our versioning policy.

Changes resulting in new major version (M.m.p)

• Removing or changing existing command line options

• Removing or changing existing REST API

• Edge case: Changing default behavior, with the old behavior still available. An example is changing the default artifact format version in mender-artifact. We have opted for upgrading the major version in this case, but this could also go into a minor release

Changes resulting in new minor version (m.M.p)

• Adding command line options

• Adding new REST API, or adding fields to responses of existing REST API

• Doing a database migration that is incompatible with the old schema (downgrade usually not possible without restoring a backup)

Changes resulting in new patch version (m.m.P)

• Any change to our Golang API. For example, the mender-artifact library has an API, used by other components, but this API is not considered public

• It should always be possible to freely upgrade and downgrade between patch versions in the same minor series

Mender Client and Yocto Project version

In general the Mender Client introduces new features in minor (e.g. 1.2.0 to 1.3.0) versions and the meta-mender layer is updated accordingly to easily support these new features (e.g. by exposing new MENDER_* variables). The meta-mender layer has branches corresponding to versions of the Yocto Project.

Clarification of the table:

• stable - recipe is maintained by Northern.tech
• community - best effort maintenance from community and Northern.tech
• no - recipe has never been released

Leverage Mender consulting services to support other versions of the Yocto Project for your board and environment.

Mender Client/Server and Artifact format

The Mender Artifact format is managed by the Mender Artifacts Library, which is included in the Mender Client and the Mender Server (for reading Artifacts) as well as in a standalone utility mender-artifact (for writing Artifacts).

Mender Server and client API

The compatibility between the Mender Server and client is managed by the Device API versions exposed by the server and used by the client. If the Mender Server supports the API version of the Mender Client, they are compatible. However, please ensure that the client and server support the Artifact format version you are using. Device API docs are available in the API chapter.

The higher version API contains a mix of old and new API endpoints. For endpoints which haven't changed in the new version the previous version ones are assumed.

Example The device supports the V2 API. It expects the single V2 endpoint to be available. For all other endpoints it will use the V1.

Mender Client and Mender connect