HiveMQ Upgrade Guide
This guide shows you how to upgrade from one HiveMQ version to another HiveMQ version.
For detailed information on HiveMQ installation, configuration, and features, see the HiveMQ User Guide.
HiveMQ uses semantic versioning for its version numbers.
Every HiveMQ version uses the following scheme:
major.minor.patch
| Rolling upgrades are supported from one minor version to the next (i.e. 4.1.x to 4.2.x). In case you want to upgrade across multiple minor version, make sure to do so in iterative steps of one minor version. (i.e. to get from 4.1.x to 4.4.x the steps are: 4.1.x to 4.2.x to 4.3.x to 4.4.x) |
Major versions are significant feature releases that add functionality that is not downward compatible with previous versions. Major versions require manual upgrade steps. Customers with professional support may be provided with tools for smooth migration. Major versions can change the extension framework and customers may need to upgrade previously-existing extensions to new APIs. Deprecated APIs can be removed in a major release. Clear documentation for the upgrade path is always provided.
Minor versions add features and functionality that is downward compatible with previous versions. Minor versions can adjust the extension framework and APIs. However, deprecated extension APIs stay in place and are not yet removed.
Patch versions (also known as bugfix releases) adjust functionality in a downward compatible manner and do not require any manual upgrade steps. These maintenance versions are drop-in replacements for the current minor version.
|
Hotfix Releases
Customers with professional support can receive hotfix releases that do not use semantic versioning.
Hotfix releases are always customer specific and are usually downward compatible.
If a hotfix version requires any manual upgrade steps, all customers who receive the hotfix version get detailed instructions.
|