Select Cypher version

antora.yml

@@ -6,4 +6,4 @@ nav:
 - modules/ROOT/content-nav.adoc
 asciidoc:
   attributes:
-    neo4j-version: '2025.05'
+    neo4j-version: '2025.06'

modules/ROOT/pages/appendix/gql-conformance/index.adoc

@@ -2,7 +2,7 @@
 = GQL conformance
 
 *Last updated*: 4 March 2025 +
-*Neo4j version*: 2025.05
+*Neo4j version*: 2025.06
 
 GQL is the new link:https://www.iso.org/home.html[ISO] International Standard query language for graph databases.
 

modules/ROOT/pages/clauses/filter.adoc

@@ -1,7 +1,7 @@
 = FILTER
 :description: Information about Cypher's `FILTER` clause.
 :table-caption!:
-:page-role: new-2025.05
+:page-role: new-2025.06
 
 `FILTER` is used to add filters to queries, similar to Cypher's xref:clauses/where.adoc[`WHERE`].
 Unlike `WHERE`, `FILTER` is not a subclause, which means it can be used independently of the xref:clauses/match.adoc[`MATCH`], xref:clauses/optional-match.adoc[`OPTIONAL MATCH`], and xref:clauses/with.adoc[`WITH`] clauses, but not within them.

modules/ROOT/pages/clauses/index.adoc

@@ -20,7 +20,7 @@ This set is refined and augmented by subsequent parts of the query.
 
 m| xref::clauses/filter.adoc[FILTER]
 | Adds filters to queries.
-label:new[Introduced in Neo4j 2025.05]
+label:new[Introduced in Neo4j 2025.06]
 
 m| xref::clauses/match.adoc[MATCH]
 | Specify the patterns to search for in the database.
@@ -45,7 +45,7 @@ m| xref::clauses/finish.adoc[FINISH]
 
 m| xref::clauses/let.adoc[LET]
 | Binds values to variables.
-label:new[Introduced in Neo4j 2025.05]
+label:new[Introduced in Neo4j 2025.06]
 
 m| xref::clauses/return.adoc[RETURN ... [AS]]
 | Defines what to include in the query result set.

modules/ROOT/pages/clauses/let.adoc

@@ -1,7 +1,7 @@
 = LET
 :description: Information about Cypher's `LET` clause.
 :table-caption!:
-:page-role: new-2025.05
+:page-role: new-2025.06
 
 `LET` binds expressions to variables.
 For queries involving several chained expressions, it can be a more succinct and readable alternative to xref:clauses/with.adoc[`WITH`].

modules/ROOT/pages/clauses/load-csv.adoc

@@ -552,7 +552,7 @@ In the file `companies.csv`, some rows do not specify values for some columns.
 The examples show several options of how to handle `null` values.
 
 [NOTE]
-The queries in this example use xref:clauses/filter.adoc#filter-with-where[`FILTER`] (introduced in Neo4j 2025.05) as a replacement for `WITH * WHERE <predicate>`.
+The queries in this example use xref:clauses/filter.adoc#filter-with-where[`FILTER`] (introduced in Neo4j 2025.06) as a replacement for `WITH * WHERE <predicate>`.
 
 .companies.csv
 [source, csv, filename="companies.csv"]

modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc

@@ -18,13 +18,11 @@ This section lists all of the features that have been removed, deprecated, added
 Replacement syntax for deprecated and removed features are also indicated.
 
 [IMPORTANT]
-Cypher 25 was introduced in Neo4j 2025.05 and can only be used on 2025.05+ databases.
-Features removed in Cypher 25 are still available on Neo4j 2025.05+ databases either by prepending a query with `CYPHER 5` or by having Cypher 5 as the default language for the database.
-For more information, see xref:queries/select-version.adoc[].
+Cypher 25 was introduced in Neo4j 2025.06 and can only be used on Neo4j 2025.06+ databases.
+Features removed in Cypher 25 are still available on Neo4j 2025.06+ databases either by prepending a query with `CYPHER 5` or by having Cypher 5 as the default language for the database.
 
-
-[[cypher-deprecations-additions-removals-2025.05]]
-== Neo4j 2025.05
+[[cypher-deprecations-additions-removals-2025.06]]
+== Neo4j 2025.06
 
 === Removed in Cypher 25
 [cols="2", options="header"]

modules/ROOT/pages/functions/index.adoc

@@ -313,7 +313,7 @@ All trigonometric functions operate on radians, unless otherwise specified.
 1.1+| xref::functions/mathematical-trigonometric.adoc#functions-cosh[`cosh()`]
 | `cosh(input :: FLOAT) :: FLOAT`
 | Returns the hyperbolic cosine of a `FLOAT`.
-label:new[Introduced in 2025.05]
+label:new[Introduced in 2025.06]
 
 1.1+| xref::functions/mathematical-trigonometric.adoc#functions-cot[`cot()`]
 | `cot(input :: FLOAT) :: FLOAT`
@@ -322,7 +322,7 @@ label:new[Introduced in 2025.05]
 1.1+| xref::functions/mathematical-trigonometric.adoc#functions-coth[`coth()`]
 | `coth(input :: FLOAT) :: FLOAT`
 | Returns the hyperbolic cotangent of a `FLOAT`.
-label:new[Introduced in 2025.05]
+label:new[Introduced in 2025.06]
 
 1.1+| xref::functions/mathematical-trigonometric.adoc#functions-degrees[`degrees()`]
 | `degrees(input :: FLOAT) :: FLOAT`
@@ -347,7 +347,7 @@ label:new[Introduced in 2025.05]
 1.1+| xref::functions/mathematical-trigonometric.adoc#functions-sinh[`sinh()`]
 | `sinh(input :: FLOAT) :: FLOAT`
 | Returns the hyperbolic sine of a `FLOAT`.
- label:new[Introduced in 2025.05]
+ label:new[Introduced in 2025.06]
 
 1.1+| xref::functions/mathematical-trigonometric.adoc#functions-tan[`tan()`]
 | `tan(input :: FLOAT) :: FLOAT`
@@ -356,7 +356,7 @@ label:new[Introduced in 2025.05]
 1.1+| xref::functions/mathematical-trigonometric.adoc#functions-tanh[`tanh()`]
 | `tanh(input :: FLOAT) :: FLOAT`
 | Returns the hyperbolic tangent of a `FLOAT`.
-label:new[Introduced in 2025.05]
+label:new[Introduced in 2025.06]
 
 |===
 

modules/ROOT/pages/functions/mathematical-trigonometric.adoc

@@ -234,7 +234,7 @@ The cosine of `0.5` is returned.
 
 ======
 
-[role=label--new-2025.05]
+[role=label--new-2025.06]
 [[functions-cosh]]
 == cosh()
 
@@ -327,7 +327,7 @@ The cotangent of `0.5` is returned.
 ======
 
 
-[role=label--new-2025.05]
+[role=label--new-2025.06]
 [[functions-coth]]
 == coth()
 
@@ -629,7 +629,7 @@ The sine of `0.5` is returned.
 ======
 
 
-[role=label--new-2025.05]
+[role=label--new-2025.06]
 [[functions-sinh]]
 == sinh()
 
@@ -723,7 +723,7 @@ The tangent of `0.5` is returned.
 
 
 
-[role=label--new-2025.05]
+[role=label--new-2025.06]
 [[functions-tanh]]
 == tanh()
 

modules/ROOT/pages/patterns/shortest-paths.adoc

@@ -64,7 +64,7 @@ CREATE (asc)-[:LINK {distance: 7.25}]->(cnm),
   (wof)-[:LINK {distance: 0.65}]->(wos)
 ----
 
-The paths matched by a xref:patterns/fixed-length-patterns.adoc#path-patterns[path pattern] can be restricted to only the shortest (by number of hops) by including the keyword `SHORTEST k`, where `k` is the number of paths to match, and can be either an `INTEGER` literal or, as of Neo4j 2025.05, a parameter which resolves to an `INTEGER`.
+The paths matched by a xref:patterns/fixed-length-patterns.adoc#path-patterns[path pattern] can be restricted to only the shortest (by number of hops) by including the keyword `SHORTEST k`, where `k` is the number of paths to match, and can be either an `INTEGER` literal or, as of Neo4j 2025.06, a parameter which resolves to an `INTEGER`.
 For example, the following example uses `SHORTEST 1` to return the length of the shortest path between `Worcester Shrub Hill` and `Bromsgrove`:
 
 .Query

modules/ROOT/pages/queries/composed-queries/combined-queries.adoc

@@ -157,7 +157,7 @@ ORDER BY count
 
 For more information, see xref:subqueries/call-subquery.adoc#call-post-union[`CALL` subqueries -> Post-union processing].
 
-[role=label--new-2025.05]
+[role=label--new-2025.06]
 [[combining-union-and-union-all]]
 == Combining UNION and UNION ALL
 

modules/ROOT/pages/queries/composed-queries/conditional-queries.adoc

@@ -1,6 +1,6 @@
 = Conditional queries (`WHEN`)
 :description: Information about how to use `WHEN` to construct conditional queries in Cypher.
-:page-role: new-2025.05
+:page-role: new-2025.06
 
 `WHEN`, together with `THEN` and `ELSE`, enables different branches of a query to execute based on certain conditions.
 In this way, it performs similar a control-flow mechanism to the `IF` statement in other programming languages.

modules/ROOT/pages/queries/composed-queries/index.adoc

@@ -8,4 +8,4 @@ As such, `UNION` and `WHEN` manage in different ways the execution flow and logi
 For more information, see:
 
 * xref:queries/composed-queries/combined-queries.adoc[]
-* xref:queries/composed-queries/conditional-queries.adoc[] label:new[Introduced in Neo4j 2025.05]
+* xref:queries/composed-queries/conditional-queries.adoc[] label:new[Introduced in Neo4j 2025.06]

modules/ROOT/pages/queries/index.adoc

@@ -9,5 +9,5 @@ It also discusses how to compose combined queries using `UNION` and conditional
 * xref:queries/select-version.adoc[]
 * xref:queries/composed-queries/index.adoc[]
 ** xref:queries/composed-queries/combined-queries.adoc[]
-** xref:queries/composed-queries/conditional-queries.adoc[] label:new[Introduced in Neo4j 2025.05]
+** xref:queries/composed-queries/conditional-queries.adoc[] label:new[Introduced in Neo4j 2025.06]
 

modules/ROOT/pages/queries/select-version.adoc

@@ -12,13 +12,13 @@ Starting in 2025, the Neo4j server transitioned to a calendar-based versioning s
 This means Neo4j will no longer use its previous semantic versioning and release pattern (e.g., 5.25, 5.26).
 Instead, releases from 2025 onwards will follow a *YYYY.MM* format, beginning with version 2025.01 released in January 2025, followed by 2025.02 released in February 2025, and so on.
 
-Cypher 25 is introduced alongside Neo4j 2025.05 and is the default language for newly created databases running version 2025.05 or later.
-However, users running Neo4j version 2025.05 or later can choose to run their queries using the previous version of Cypher: Cypher 5.
-If so, Neo4j will use Cypher as it existed at the time of the Neo4j 5.26 long-term support (LTS) release.
+Cypher 25 is introduced alongside Neo4j 2025.06.
+However, users running Neo4j version 2025.06 or later can choose to run their queries using the previous version of Cypher: Cypher 5.
+If so, Neo4j will use Cypher as it existed at the time of the Neo4j **TBC** release.
 
-[NOTE]
-Databases migrating to Neo4j 2025.05+ from earlier versions will continue to use Cypher 5 as their default language.
-To change the default language on such databases, see xref:queries/select-version.adoc#alter-default-cypher-version[Alter the default Cypher version for a database].
+[IMPORTANT]
+All new databases created after the release of 2025.06 will continue to use Cypher 5 as their default language.
+To change the default language, see xref:queries/select-version.adoc#alter-default-cypher-version[Alter the default Cypher version for a database].
 See also xref:queries/select-version.adoc#config-database-upgrades[Cypher versions, configuration settings, and DBMS upgrades] for information about what default Cypher version is used when upgrading a DBMS.
 
 For information about updates to Cypher in different Neo4j versions, see xref:deprecations-additions-removals-compatibility.adoc[].
@@ -29,10 +29,10 @@ For information about Cypher 5, see the link:https://neo4j.com/docs/cypher-manua
 
 To select the Cypher version of a query, prepend it with `CYPHER <language version>`. 
 
-Selecting `CYPHER 5` ensures that the query will be executed using the language as it existed at the time of the Neo4j 5.26 LTS release.
-Any changes introduced after 5.26 will not affect the query.
+Selecting `CYPHER 5` ensures that the query will be executed using the language as it existed at the time of the Neo4j **TBC** release.
+Any changes introduced after the **TBC** release will not affect the query.
 
-Selecting `CYPHER 25` ensures that the query will be executed using the language as it exists in the version of Neo4j that the database is currently running, provided it is on Neo4j 2025.05 or later.
+Selecting `CYPHER 25` ensures that the query will be executed using the language as it exists in the version of Neo4j that the database is currently running, provided it is on Neo4j 2025.06 or later.
 
 Below are two examples showing the two versions of Cypher behaving differently.
 
@@ -115,13 +115,13 @@ For example, if a database is created with Cypher 5 as its default language, pre
 === Procedures and functions
 
 link:{neo4j-docs-base-uri}/operations-manual/current/procedures[Procedures] and xref:functions/index.adoc[functions] (including built-in and link:{neo4j-docs-base-uri}/apoc/current/[APOC]) are tied to a specific Cypher language version.
-Therefore, procedures and functions in Neo4j 2025.05+ and APOC 2025.05+ (both of which have Cypher 25 as their default language) may behave differently depending on what version of Cypher is used.
+Therefore, procedures and functions in Neo4j 2025.06+ and APOC 2025.06+ (both of which have Cypher 5 as their default language) may behave differently depending on what version of Cypher is used.
 
-For example, APOC 2025.05 removed Cypher 25 support of the procedure `apoc.create.uuids()`, meaning it is not available to queries running Cypher 25.
-However, it can still be used on APOC 2025.05 if queries are prepended with `CYPHER 5`, or if the database’s default version is set to `CYPHER 5`.
-In this case, Neo4j will use APOC and Cypher as they existed at the time of the 5.26 LTS release.
+For example, APOC 2025.06 removed Cypher 25 support of the procedure `apoc.create.uuids()`, meaning it is not available to queries running Cypher 25.
+However, it can still be used on APOC 2025.06 if queries are prepended with `CYPHER 5`, or if the database’s default version is set to `CYPHER 5`.
+In this case, Neo4j will use APOC and Cypher as they existed at the time of the **TBC** release.
 
-.Using a procedure removed in Cypher 25 with APOC 2025.05+
+.Using a procedure removed in Cypher 25 with APOC 2025.06+
 [source, cypher]
 ----
 CYPHER 5
@@ -145,22 +145,22 @@ RETURN n.name
 [[select-default-cypher-version]]
 == Select the default Cypher version when creating a database
 
-Databases created on Neo4j 2025.05 or later will have Cypher 25 as their default language (if {neo4j-docs-base-uri}/operations-manual/current/configuration/configuration-settings/#config_db.query.default_language[`config_db.query.default_language`] is set to `CYPHER_25` -- see  xref:queries/select-version.adoc#config-database-upgrades[Cypher versions, configuration settings, and DBMS upgrades] below).
-This is true for the link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/#manage-database-systems[system, standard, and composite] Neo4j databases.
+Databases created on Neo4j 2025.06 or later will continue to have Cypher 5 as their default language (if {neo4j-docs-base-uri}/operations-manual/current/configuration/configuration-settings/#config_db.query.default_language[`config_db.query.default_language`] is set to `CYPHER 5` -- see  xref:queries/select-version.adoc#config-database-upgrades[Cypher versions, configuration settings, and DBMS upgrades] below).
+This is true for link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/#manage-database-systems[system, standard, and composite] Neo4j databases.
 
 To select a different default Cypher version for a database, add `DEFAULT LANGUAGE <language version>` to the link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/standard-databases/create-databases/[`CREATE DATABASE`] statement.
 This can be done on any Neo4j database.
 
-Selecting `CYPHER 5` as the default database language ensures that every query run on that database uses the language as it existed at the time of the Neo4j 5.26 LTS release (unless a query is prepended with `CYPHER 25`, which overrides this default).
-Any changes introduced after 5.26 will not affect the semantics of the query.
+Selecting `CYPHER 5` as the default database language ensures that every query run on that database uses the language as it existed at the time of the Neo4j **TBC** release (unless a query is prepended with `CYPHER 25`, which overrides this default).
+Any changes introduced after the **TBC** release will not affect the semantics of the query.
 
 .Create a database with Cypher 5 as the default language
 [source, cypher]
 ----
 CREATE DATABASE my_database DEFAULT LANGUAGE CYPHER 5
 ----
 
-Selecting `CYPHER 25` ensures that the query will be executed using the language as it exists in the version of Neo4j that the database is currently running, provided it is on Neo4j 2025.05 or later (unless a query is prepended with `CYPHER 5`, which overrides this default).
+Selecting `CYPHER 25` ensures that the query will be executed using the language as it exists in the version of Neo4j that the database is currently running, provided it is on Neo4j 2025.06 or later (unless a query is prepended with `CYPHER 5`, which overrides this default).
 
 .Create a database with Cypher 25 as the default language
 [source, cypher]
@@ -230,22 +230,22 @@ The table below outlines which Cypher version is assigned to databases in differ
 |===
 | Scenario | `db.query.default_language` | Databases
 
-| *Standard DBMS upgrade to Neo4j 2025.05+*
+| *Standard DBMS upgrade to Neo4j 2025.06+*
 | Unset
 | *Existing system database:* `CYPHER 5` +
 *Existing user databases:* `CYPHER 5` +
 *New user databases default:* `CYPHER 5`
 
-| *Custom DBMS upgrade to Neo4j 2025.05+*
-| Manually set to `CYPHER_25` by administrator
+| *Custom DBMS upgrade to Neo4j 2025.06+*
+| Manually set to `CYPHER 25` by administrator
 | *Existing system database:* `CYPHER 5` +
 *Existing user databases:* `CYPHER 5`  +
 *New user databases default:* `CYPHER 25`
 
-| *New installation of Neo4j 2025.05+* 
-| Set to `CYPHER_25`
-| *New system database:* `CYPHER 25` +
-*New user databases default:* `CYPHER 25`
+| *New installation of Neo4j 2025.06+* 
+| Set to `CYPHER 5`
+| *New system database:* `CYPHER 5` +
+*New user databases default:* `CYPHER 5`
 
 |===
 

modules/ROOT/pages/subqueries/call-subquery.adoc

@@ -484,7 +484,7 @@ Now all `Player` nodes, regardless of whether they have any `PLAYS_FOR` relation
 
 ====
 
-[role=label--new-2025.05]
+[role=label--new-2025.06]
 [[conditional-call]]
 == Conditional `CALL` subqueries
 

modules/ROOT/pages/subqueries/collect.adoc

@@ -74,7 +74,7 @@ RETURN person.name as name, COLLECT {
 2+d|Rows: 3
 |===
 
-[role=label--new-2025.05]
+[role=label--new-2025.06]
 [[conditional-collect]]
 == Conditional `COLLECT` subquery
 

modules/ROOT/pages/subqueries/count.adoc

@@ -71,7 +71,7 @@ RETURN person.name AS name
 1+d|Rows: 1
 |===
 
-[role=label--new-2025.05]
+[role=label--new-2025.06]
 [[conditional-count]]
 == Conditional `COUNT` subquery
 

modules/ROOT/pages/subqueries/existential.adoc

@@ -73,7 +73,7 @@ RETURN person.name AS name
 1+d|Rows: 1
 |===
 
-[role=label--new-2025.05]
+[role=label--new-2025.06]
 [[conditional-exists]]
 == Conditional `EXISTS` subqueries
 

modules/ROOT/pages/subqueries/subqueries-in-transactions.adoc

@@ -934,8 +934,7 @@ RETURN status.transactionId AS transaction, status.committed AS commitStatus, st
 These are transient errors, meaning that re-running the transactions may be successful.
 To retry the any failed inner transactions, use the error option `ON ERROR RETRY`, which retries any failing transactions until the maximum retry duration has been reached.
 
-[NOTE]
-The query below uses xref:clauses/filter.adoc#filter-with-where[`FILTER`] (introduced in Neo4j 2025.05) as a replacement for `WITH * WHERE <predicate>`.
+The following query uses `ON ERROR RETRY ... THEN CONTINUE` to retry the above query for a maximum of `3` seconds and then continue the execution of subsequent inner transactions by ignoring any recoverable errors.
 
 .Query using `ON ERROR RETRY ... THEN CONTINUE` to retry deadlocked inner transactions and complete outer transaction
 [source, cypher]