Version compatibility
Versioning scheme
Neo4j Ops Manager follows semantic versioning for its releases.
-
A major release can include breaking changes across NOM server and NOM agent features.
-
A minor release can include non-breaking changes and improvements to old features, and may include new features for NOM server, NOM agent, or both.
-
A patch release is usually for bug fixes and hot-fix features.
Compatibility matrix
Every Neo4j Ops Manager release relies on compatible subsystems and monitored Neo4j DBMSs for optimal functionality. Following table details the compatibility matrix for NOM:
| NOM Release | NOM Server | NOM Agent | NOM Persistence (Neo4j Enterprise) | Neo4j DBMS |
|---|---|---|---|---|
1.0.0 |
1.0.0 |
1.0.0 |
>4.4.2 |
>4.4.2 |
1.1.0 |
1.1.0 |
1.1.0 |
>4.4.2 |
>4.4.2 |
1.1.1 |
1.1.1 |
1.1.1 |
>4.4.2 |
>4.4.2 |
1.2.1 |
1.2.1 |
1.2.1 |
>4.4.2, 5.1.0 |
>4.4.2, 5.1.0 |
1.3.x |
1.3.x |
1.3.x |
>4.4.2, >5.1.0 |
>4.4.2 (Query log feature not available for 4.4.x DBMSs), >5.1.0 |
1.4.x |
1.4.x |
1.4.x |
>4.4.2, >5.1.0 |
>4.4.2 (Query log feature not available for 4.4.x DBMSs), >5.1.0 |
1.5.x |
1.5.x |
1.5.x |
>4.4.2, >5.1.0 |
>4.4.2 (Query log feature not available for 4.4.x DBMSs), >5.1.0 |
Was this page helpful?