Upgrade from older versions
This page contains the list of new features and breaking changes of the driver from version 5.28 to 6.x. For a full list of changes, see the driver changelog.
The latest driver version of the 6.x series is compatible with Neo4j server both 4.4, 5.x, and 202[56].x, so you can upgrade the driver before you upgrade the server. At the same time, the driver version 5.28 is forward compatible with Neo4j server 202[56].x, so you could also upgrade the server before the driver; however, given that it’s easier to roll back an application upgrade than a server upgrade, it’s recommended to start with the driver.
When upgrading the Neo4j server to a newer version, the Cypher queries in your application might also need updating.
The Drivers Migration Assistent doesn’t cover Cypher changes. See Cypher → Deprecations, additions, and compatibility. |
New features
New type
|
GQL status objects in errorsError objects also expose errors as GQL-status objects. The main difference between Neo4j error codes and GQL error codes is that the latter are more granular. For more information, see Error handling. |
Breaking changes and deprecations
Deprecated features are likely to be removed in the next major version.
Version | Message | Status |
---|---|---|
6.0 |
Through the new methods, the first argument of transaction functions is a |
Removed |
6.0 |
|
Removed |
6.0 |
|
Removed |
6.0 |
|
Removed |
6.0 |
|
Changed |
6.0 |
|
Changed |
5.0 |
|
Deprecated |
5.0 |
|
Deprecated |
6.0 |
|
Deprecated |
6.0 |
|
Deprecated |
6.0 |
Notifications as Neo4j status codes are deprecated in favor of GQL status objects. As a result,
|
Deprecated |
6.0 |
|
Deprecated |