Introduction

This Guide is an addendum to the official documentation and shows all upgrade steps from one HiveMQ version to another.

HiveMQ uses Semantic Versioning for its version numbers.

Every HiveMQ version uses the following scheme:

major.minor.patch
major

Major versions are not downward compatible with previous versions. These are major feature releases and manual upgrade instructions need to be applied. Customers with professional support may be provided with tools for smooth migration. The extension system interfaces may change and customers may need to upgrade their extensions to new APIs. The upgrade path is always clearly documented. Deprecated APIs may be removed in major releases.

minor

Minor versions are typically feature releases with downward compatible changes. The extension system may receive upgrades and new APIs. Old APIs may be deprecated and may be removed in a later major version. Deprecated extension APIs stay in place and won’t get removed.

patch

Patch releases (also known as bugfix releases) don’t need manual upgrade steps and are drop-in replacements for the current minor version.

Hotfix Releases
Customers with professional support can receive hotfix releases which don’t use semantic versioning. These hotfix releases are always customer specific and are typically downward compatible. All customers which receive hotfix versions get detailed instructions if manual upgrade steps are needed.