Neo4j 2025.01 has been released today on neo4j.com, and will be available shortly in all the usual repositories and marketplaces including Docker, Helm Charts, AWS, Azure and GCP. This release includes the following features:
New supported platforms - MacOS 13, 14, 15, Ubuntu 24.04, Windows Server 2025, Red Hat (RHEL) 9.4.
Introduction of dbms.unquarantineDatabase procedure.
SSL/TLS hostname verification is now enabled by default.
Full details of the new features and fixes are available in the Release Note.
Please refer to the changelog for full details of the changes.
Announcement Neo4j 2025.03 has been released yesterday on neo4j.com, and will be available shortly in all the usual repositories and marketplaces including Docker, Helm Charts, AWS, Azure and GCP. This release includes the following features:
Dynamic TLS Certificate Rotation
New error handling mode for CALL IN TRANSACTIONS: ON ERROR RETRY
Full details of the new features and fixes are available in the Release Note. Please refer to the changelog for full details of the changes.
Neo4j 2025.04 has been released today on neo4j.com, and will be available shortly in all the usual repositories and marketplaces including Docker, Helm Charts, AWS, Azure and GCP. This release includes the following features:
Property-based access control for relationships.
Updated dbms.components() procedure to return the calendar version of Neo4j.
Introduce --error-format argument to Cypher Shell to control how errors are displayed.
Updated CDC change event IDs so they work with a database recovered using dbms.recreateDatabase().
A database alias can now be used as default database.
Full details of the new features and fixes are available in the Release Note. Please refer to the changelog for full details of the changes.
Neo4j 4.4 and 5.26 are designated as LTS releases. LTS releases have a three-year support window during which they receive critical patches and security updates but not new features or improvements. Neo4j 4.4 will be supported until November 2025 and Neo4j 5 until November 2028.
Announcement Neo4j 2025.05 has been released today on neo4j.com, and will be available shortly in all the usual repositories and marketplaces including Docker, Helm Charts, AWS, Azure and GCP. This release includes the following features:
dbms.components() procedure will now also include the supported cypher versions.
a fix for a bug in pipelined runtime, where in certain scenarios cached properties in an OPTIONAL MATCH were not properly cleared between rows, which could lead to incorrect results.
Full details of the new features and fixes are available in the Release Note.
Please refer to the changelog for full details of the changes.
Neo4j 2025.06 has been released today on neo4j deployment center, and will be available shortly in all the usual repositories and marketplaces including Docker, Helm Charts, AWS, Azure and GCP. This release includes the following features:
Introduction of Cypher versioning
Full details of the new features and fixes are available in the Release Note.
Please refer to the changelog for full details of the changes.
Neo4j 2025.06.1 has been released on neo4j.com/deployment-center/, and will shortly be available in all the usual repositories and marketplaces including Docker, Helm Charts, AWS, Azure and GCP. This is a maintenance release containing fixes and new bundled packages.
Full details of the release are available in the Release Notes. Please refer to the changelog for full details of the changes.
Neo4j 2025.06.2 has been released on neo4j.com/deployment-center/, and will shortly be available in all the usual repositories and marketplaces including Docker, Helm Charts, AWS, Azure and GCP. This is a maintenance release containing fixes and new bundled packages.
This patch includes the tcnative libraries missing in 2025.06.1
Full details of the release are available in the Release Notes.
Neo4j 2025.07 has been released today on neo4j deployment center, and will be available shortly in all the usual repositories and marketplaces including Docker, Helm Charts, AWS, Azure and GCP. This release includes the following features:
Introduction of Cypher versioning
Full details of the new features and fixes are available in the Release Note.
Please refer to the changelog for full details of the changes.
Neo4j 2025.07.01 has been released today on neo4j deployment center, and will be available shortly in all the usual repositories and marketplaces including Docker, AWS, Azure and GCP. This release is a hotfix release that fixes a connectivity regression issue.
Full details of the new features and fixes are available in the Release Note.
Please refer to the changelog for full details of the changes.
Neo4j 2025.08 has been released today on neo4j deployment center, and will be available shortly in all the usual repositories and marketplaces including Docker, Helm Charts, AWS, Azure and GCP. This release includes the following features:
Full details of the new features and fixes are available in the Release Note.
Please refer to the changelog for full details of the changes.
Neo4j 2025.09 has been released today on neo4j deployment center, and will be available shortly in all the usual repositories and marketplaces including Docker, Helm Charts, AWS, Azure and GCP. Full details of the new features and fixes are available in the Release Note.
Please refer to the changelog for full details of the changes.
Neo4j 2025.11.2 has been released today on Neo4j Deployment Center, and will be available shortly in all the usual repositories and marketplaces, including Docker, Helm Charts, AWS, Azure, and GCP. Full details of the new features and fixes are available in the Release Note.
Neo4j 2025.12.1 has been released today on Neo4j Deployment Center, and will be available shortly in all the usual repositories and marketplaces, including Docker, Helm Charts, AWS, Azure, and GCP. Full details of the new features and fixes are available in the Release Note.
Please refer to the changelog for full details of the changes.
Important Notice: We have identified a bug in Dynamic Node Labels and Dynamic Relationship Types when used with composite (multi-property) indexes which can lead to the operator sometimes returning incorrect MATCH results. When used in a MERGE, this can potentially result in updates to the incorrect node, or in the runtime issuing CREATE operations that cannot succeed. This bug was introduced in 2025.11. A fix will be released shortly, but in the meantime we advise customers not to use Dynamic Label/Relationship Types in conjunction with composite indexes.
Important Update: We recently issued a notification about a bug in Dynamic Node Labels and Dynamic Relationship Types when used with composite (multi-property) indexes which can lead to the operator sometimes returning incorrect MATCH results. When used in a MERGE, this can potentially result in updates to the incorrect node, or in the runtime issuing CREATE operations that cannot succeed.
This bug, introduced in 2025.11, has been fixed in the new 2026.01.4 release which is available for download now from the Neo4j Deployment Center. We advise anyone using Dynamic Label/Relationship Types in conjunction with composite indexes to upgrade at the earliest opportunity.
