Merge branch 'dev' into dev-lock-nodes-op

JPryce-Aklundh · web-flow · commit 6a1be1cd1f78 · 2025-09-03T10:38:22.000+02:00
diff --git a/antora.yml b/antora.yml
@@ -7,4 +7,4 @@ nav:
 - modules/ROOT/content-nav.adoc
 asciidoc:
   attributes:
-    neo4j-version: '2025.08'
+    neo4j-version: '2025.09'
diff --git a/modules/ROOT/pages/appendix/gql-conformance/additional-cypher.adoc b/modules/ROOT/pages/appendix/gql-conformance/additional-cypher.adoc
@@ -330,6 +330,10 @@ It is only supported in the xref:clauses/use.adoc[`USE`] clause.
 | xref:functions/predicate.adoc#functions-all[`all()`]
 | Returns true if the predicate holds for all elements in the given `LIST<ANY>`.
 
+| xref:functions/predicate.adoc#functions-allreduce[`allReduce()`]
+|  Returns true if, during the stepwise evaluation of a value across the elements in a given `LIST<ANY>`, the accumulated result satisfies a specified predicate at every step.
+Where that list is a group variable defined in a quantified path pattern, it allows for the early pruning of paths that do not satisfy the predicate.
+
 | xref:functions/predicate.adoc#functions-any[`any()`]
 | Returns true if the predicate holds for at least one element in the given `LIST<ANY>`.
 
diff --git a/modules/ROOT/pages/appendix/gql-conformance/index.adoc b/modules/ROOT/pages/appendix/gql-conformance/index.adoc
@@ -1,8 +1,8 @@
 :description: Overview of Cypher's conformance to GQL.
 = GQL conformance
 
-*Last updated*: 18 June 2025 +
-*Neo4j version*: 2025.06
+*Last updated*: 2 September 2025 +
+*Neo4j version*: 2025.08
 
 GQL is the new link:https://www.iso.org/home.html[ISO] International Standard query language for graph databases.
 
diff --git a/modules/ROOT/pages/clauses/filter.adoc b/modules/ROOT/pages/clauses/filter.adoc
@@ -1,7 +1,7 @@
 = FILTER
 :description: Information about Cypher's `FILTER` clause.
 :table-caption!:
-:page-role: new-2025.06
+:page-role: new-neo4j-2025.06 cypher-25-only
 
 `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.
diff --git a/modules/ROOT/pages/clauses/index.adoc b/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.06]
+label:cypher[Cypher 25 only] 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.06]
+ label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.06]
 
 m| xref::clauses/return.adoc[RETURN ... [AS]]
 | Defines what to include in the query result set.
diff --git a/modules/ROOT/pages/clauses/let.adoc b/modules/ROOT/pages/clauses/let.adoc
@@ -1,7 +1,7 @@
 = LET
 :description: Information about Cypher's `LET` clause.
 :table-caption!:
-:page-role: new-2025.06
+:page-role: new-neo4j-2025.06 cypher-25-only
 
 `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`].
diff --git a/modules/ROOT/pages/clauses/match.adoc b/modules/ROOT/pages/clauses/match.adoc
@@ -494,7 +494,7 @@ RETURN actors.name AS actor, movieCount, collect(movies.title) AS movies
 <1> The `Person` and `Movie` nodes matched in this step are stored in variables, which are then passed on to the second row of the query.
 <2> The `movies` variable is implicitly imported by its occurrence in the `count()` function.
 The `WITH` clause explicitly imports the `actors` variable.
-<3> An xref:clauses/order-by.adoc[`ORDER BY`] clause orders the results by `movieCount` in descending order, ensuring that the `Person` with the highest number of movies appears at the top, and xref:clauses/limit.adoc[`LIMIT] 1` ensures that all other `Person` nodes are discarded.
+<3> An xref:clauses/order-by.adoc[`ORDER BY`] clause orders the results by `movieCount` in descending order, ensuring that the `Person` with the highest number of movies appears at the top, and xref:clauses/limit.adoc[`LIMIT`] `1` ensures that all other `Person` nodes are discarded.
 <4> The second `MATCH` clause finds all `Movie` nodes associated with the `Person` nodes currently bound to the `actors` variable.
 
 [NOTE]
diff --git a/modules/ROOT/pages/clauses/remove.adoc b/modules/ROOT/pages/clauses/remove.adoc
@@ -66,7 +66,7 @@ Properties set: 1
 == Remove all properties
 
 `REMOVE` cannot be used to remove all existing properties from a node or relationship.
-Instead, using xref::clauses/set.adoc#set-remove-properties-using-empty-map[`SET` with `=` and an empty map as the right operand] will clear all properties from the node or relationship.
+Instead, using xref::clauses/set.adoc#set-remove-properties-using-empty-map[`SET`] with `=` and an empty map as the right operand will clear all properties from the node or relationship.
 
 [[dynamic-remove-property]]
 == Dynamically remove a property
@@ -152,7 +152,7 @@ REMOVE n:$(label)
 RETURN n.name, labels(n)
 ----
 
-<1> xref:clauses/unwind.adoc[`UNWIND`] is used here to transform the list of labels from the xref:functions/list.adoc#functions-labels[`labels()]` function into separate rows, allowing subsequent operations to be performed on each label individually.
+<1> xref:clauses/unwind.adoc[`UNWIND`] is used here to transform the list of labels from the xref:functions/list.adoc#functions-labels[`labels()`] function into separate rows, allowing subsequent operations to be performed on each label individually.
 
 .Result
 [role="queryresult",options="header,footer",cols="2*<m"]
diff --git a/modules/ROOT/pages/clauses/with.adoc b/modules/ROOT/pages/clauses/with.adoc
@@ -339,7 +339,7 @@ ORDER BY discountRates
 1+d|Rows: 5
 |===
 
-[role=label--new-2025.06]
+[role=label--new-Neo4j-2025.06 label--cypher-25-only]
 [[with-all-results]]
 == Explicitly project values
 
diff --git a/modules/ROOT/pages/expressions/conditional-expressions.adoc b/modules/ROOT/pages/expressions/conditional-expressions.adoc
@@ -111,7 +111,7 @@ implied equals (`=`) comparator.
 The supported comparators are:
 
 * xref:expressions/predicates/comparison-operators.adoc[Regular Comparison Operators]: `+=+`, `+<>+`, `+<+`, `+>+`, `+<=+`, `+>=+`
-* xref:expressions/predicates/comparison-operators.adoc[`IS [NOT] NULL`]
+* xref:expressions/predicates/comparison-operators.adoc[`IS [NOT\] NULL`]
 * xref:expressions/predicates/type-predicate-expressions.adoc[Type predicate expressions]: `IS [NOT] TYPED <TYPE>` (Note that the form `IS [NOT] :: <TYPE>` is not accepted)
 * xref:expressions/predicates/string-operators.adoc[Normalization Predicate Expression]: `IS [NOT] NORMALIZED`
 * xref:expressions/predicates/string-operators.adoc[String Comparison Operators]: `STARTS WITH`, `ENDS WITH`, `=~` (regex matching)
diff --git a/modules/ROOT/pages/functions/index.adoc b/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 Neo4j 2025.06]
+label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.06]
 
 1.1+| xref::functions/mathematical-trigonometric.adoc#functions-cot[`cot()`]
 | `cot(input :: FLOAT) :: FLOAT`
@@ -322,7 +322,7 @@ label:new[Introduced in Neo4j 2025.06]
 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 Neo4j 2025.06]
+label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.06]
 
 1.1+| xref::functions/mathematical-trigonometric.adoc#functions-degrees[`degrees()`]
 | `degrees(input :: FLOAT) :: FLOAT`
@@ -347,7 +347,7 @@ label:new[Introduced in Neo4j 2025.06]
 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 Neo4j 2025.06]
+label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.06]
 
 1.1+| xref::functions/mathematical-trigonometric.adoc#functions-tan[`tan()`]
 | `tan(input :: FLOAT) :: FLOAT`
@@ -356,7 +356,7 @@ label:new[Introduced in Neo4j 2025.06]
 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 Neo4j 2025.06]
+label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.06]
 
 |===
 
@@ -377,7 +377,7 @@ These functions return either true or false for the given arguments.
 1.1+| xref::functions/predicate.adoc#functions-allreduce[`allReduce()`]
 | `allReduce(accumulator = initial, stepVariable IN list \| reductionFunction, predicate) :: BOOLEAN`
 | Returns true if, during the stepwise evaluation of a value across the elements in a given `LIST<ANY>`, the accumulated result satisfies a specified predicate at every step.
-Where that list is a group variable defined in a quantified path pattern, it allows for the early pruning of paths that do not satisfy the predicate. label:new[Introduced in Neo4j 2025.08]
+Where that list is a group variable defined in a quantified path pattern, it allows for the early pruning of paths that do not satisfy the predicate. label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.08]
 
 1.1+| xref::functions/predicate.adoc#functions-any[`any()`]
 | `any(variable :: ANY, list :: LIST<ANY>, predicate :: ANY) :: BOOLEAN`
diff --git a/modules/ROOT/pages/functions/mathematical-trigonometric.adoc b/modules/ROOT/pages/functions/mathematical-trigonometric.adoc
@@ -234,7 +234,7 @@ The cosine of `0.5` is returned.
 
 ======
 
-[role=label--new-2025.06]
+[role=label--new-Neo4j-2025.06 label--cypher-25-only]
 [[functions-cosh]]
 == cosh()
 
@@ -327,7 +327,7 @@ The cotangent of `0.5` is returned.
 ======
 
 
-[role=label--new-2025.06]
+[role=label--new-Neo4j-2025.06 label--cypher-25-only]
 [[functions-coth]]
 == coth()
 
@@ -629,7 +629,7 @@ The sine of `0.5` is returned.
 ======
 
 
-[role=label--new-2025.06]
+[role=label--new-Neo4j-2025.06 label--cypher-25-only]
 [[functions-sinh]]
 == sinh()
 
@@ -723,7 +723,7 @@ The tangent of `0.5` is returned.
 
 
 
-[role=label--new-2025.06]
+[role=label--new-Neo4j-2025.06 label--cypher-25-only]
 [[functions-tanh]]
 == tanh()
 
diff --git a/modules/ROOT/pages/functions/predicate.adoc b/modules/ROOT/pages/functions/predicate.adoc
@@ -103,7 +103,7 @@ RETURN all(i in emptyList WHERE true) as allTrue, all(i in emptyList WHERE false
 ======
 
 [[functions-allreduce]]
-[role=label--new-2025.08]
+[role=label--new-2025.08 label--cypher-25-only]
 == allReduce()
 
 .Details
diff --git a/modules/ROOT/pages/introduction/cypher-neo4j.adoc b/modules/ROOT/pages/introduction/cypher-neo4j.adoc
@@ -52,7 +52,7 @@ Only xref::planning-and-tuning/runtimes/concepts.adoc#runtimes-slotted-runtime[s
 [NOTE]
 The `system` database cannot be deleted.
 The default user database, `neo4j`, can be deleted.
-If you want to delete it, first set another database as the default using the procedure link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_dbms_setDefaultDatabase[`dbms.setDefaultDatabase]` (this must be done from the `system` database).
+If you want to delete it, first set another database as the default using the procedure link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_dbms_setDefaultDatabase[`dbms.setDefaultDatabase`] (this must be done from the `system` database).
 For more information, see the link:{neo4j-docs-base-uri}/operations-manual/current/clustering/databases/#cluster-default-database[Operations Manual -> Change the default database].
 
 
diff --git a/modules/ROOT/pages/patterns/match-modes.adoc b/modules/ROOT/pages/patterns/match-modes.adoc
@@ -9,7 +9,7 @@ Cypher supports two match modes:
 The same restriction does not hold for nodes, which may be re-traversed any number of times in a matched path.
 This is Cypher’s default match mode, applicable to most use cases.
 * xref:patterns/match-modes.adoc#repeatable-elements[`REPEATABLE ELEMENTS`]: no restrictions on how often nodes and relationships can be traversed in a match for a graph pattern.
-This match mode is required in order for paths to be able to traverse a relationship more than once. label:new[Introduced in Neo4j 2025.06]
+This match mode is required in order for paths to be able to traverse a relationship more than once. label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.06]
 
 [[example-graph]]
 == Example graph
@@ -47,7 +47,8 @@ As such, `DIFFERENT RELATIONSHIPS` is ideal to showcase the Königsberg bridges
 That is, if no match mode is specified, Cypher will default to solving graph patterns according to the restrictions imposed by `DIFFERENT RELATIONSHIPS`.
 
 [NOTE]
-The `DIFFERENT RELATIONSHIPS` keyword was released in Neo4j 2025.06 and can be used to explicitly specify Cypher's default match mode after `MATCH`.
+The `DIFFERENT RELATIONSHIPS` keyword was released in Neo4j 2025.06.
+It is only available in Cypher 25 and can be used to explicitly specify Cypher's default match mode after `MATCH`.
 For example, `MATCH DIFFERENT RELATIONSHIPS p = (start)--{,2}(end)`.
 This is functionally equivalent to not specifying a match mode.
 
@@ -141,7 +142,7 @@ This reflects the conclusion of Euler’s Seven bridges of Königsberg problem:
 
 For more information about this match mode, see xref:patterns/reference.adoc#match-modes-rules-different-relationships[Syntax & semantics -> `DIFFERENT RELATIONSHIPS`].
 
-[role=label--new-2025.06]
+[role=label--new-Neo4j-2025.06 label--cypher-25-only]
 [[repeatable-elements]]
 == REPEATABLE ELEMENTS
 
diff --git a/modules/ROOT/pages/patterns/reference.adoc b/modules/ROOT/pages/patterns/reference.adoc
@@ -1637,7 +1637,7 @@ MATCH ()-[r]->()-->(), ()-[r]-()
 A match mode specifies whether or not a relationship can be matched more than once when matching graph patterns. Cypher contains two match modes:
 
 * xref:patterns/reference.adoc#match-modes-rules-different-relationships[`DIFFERENT RELATIONSHIPS`] (default)
-* xref:patterns/reference.adoc#match-modes-rules-repeatable-elements[`REPEATABLE ELEMENTS`] label:new[Introduced in Neo4j 2025.06]
+* xref:patterns/reference.adoc#match-modes-rules-repeatable-elements[`REPEATABLE ELEMENTS`] label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.06]
 
 [[match-modes-syntax]]
 === Syntax
@@ -1674,7 +1674,8 @@ MATCH (a)-[r]-(b)-[f]-(c)-[r]-(d)  // r repeated twice
 MATCH (a)-[r]-(b), (c)-[r]-(d)     // r repeated twice
 ----
 
-The `DIFFERENT RELATIONSHIPS` keyword was released in Neo4j 2025.06 and can be used to explicitly specify Cypher's default match mode after `MATCH`.
+The `DIFFERENT RELATIONSHIPS` keyword was released in Neo4j 2025.06.
+It is only available in Cypher 25 and can be used to explicitly specify Cypher's default match mode after `MATCH`.
 Specifying the `DIFFERENT RELATIONSHIPS` keyword is functionally equivalent to not specifying a match mode.
 For example, the following two `MATCH` clauses are equivalent:
 
@@ -1684,6 +1685,7 @@ MATCH (a)--{2}(b)
 MATCH DIFFERENT RELATIONSHIPS (a)--{2}(b)
 ----
 
+[role=label--new-Neo4j-2025.06 label--cypher-25-only]
 [[match-modes-rules-repeatable-elements]]
 ==== REPEATABLE ELEMENTS
 
diff --git a/modules/ROOT/pages/queries/composed-queries/combined-queries.adoc b/modules/ROOT/pages/queries/composed-queries/combined-queries.adoc
@@ -164,7 +164,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.06]
+[role=label--new-Neo4j-2025.06 label--cypher-25-only]
 [[combining-union-and-union-all]]
 == Combining UNION and UNION ALL
 
diff --git a/modules/ROOT/pages/queries/composed-queries/conditional-queries.adoc b/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.06
+:page-role: new-neo4j-2025.06 cypher-25-only
 
 `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.
diff --git a/modules/ROOT/pages/queries/composed-queries/index.adoc b/modules/ROOT/pages/queries/composed-queries/index.adoc
@@ -10,5 +10,5 @@ As such, `UNION`, `WHEN`, and `NEXT` manage in different ways the execution flow
 For more information, see:
 
 * xref:queries/composed-queries/combined-queries.adoc[]
-* xref:queries/composed-queries/conditional-queries.adoc[] label:new[Introduced in Neo4j 2025.06]
-* xref:queries/composed-queries/sequential-queries.adoc[] label:new[Introduced in Neo4j 2025.06]
+* xref:queries/composed-queries/conditional-queries.adoc[] label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.06]
+* xref:queries/composed-queries/sequential-queries.adoc[] label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.06]
diff --git a/modules/ROOT/pages/queries/composed-queries/sequential-queries.adoc b/modules/ROOT/pages/queries/composed-queries/sequential-queries.adoc
@@ -1,7 +1,7 @@
 = Sequential queries (`NEXT`)
 :description: Information about how to use `NEXT` to construct sequential queries in Cypher.
 :table-caption!:
-:page-role: new-2025.06
+:page-role: new-neo4j-2025.06 cypher-25-only
 
 `NEXT` allows for linear composition of queries into a sequence of smaller, self-contained segments, passing the whole table of intermediate results from one segment to the next.
 
diff --git a/modules/ROOT/pages/queries/index.adoc b/modules/ROOT/pages/queries/index.adoc
@@ -9,6 +9,6 @@ It also explains how to select the version of Cypher in which queries are run, a
 * xref:queries/select-version.adoc[] label:new[Introduced in Neo4j 2025.06]
 * 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.06]
-** xref:queries/composed-queries/sequential-queries.adoc[] label:new[Introduced in Neo4j 2025.06]
+** xref:queries/composed-queries/conditional-queries.adoc[] label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.06]
+** xref:queries/composed-queries/sequential-queries.adoc[] label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.06]
 
diff --git a/modules/ROOT/pages/subqueries/call-subquery.adoc b/modules/ROOT/pages/subqueries/call-subquery.adoc
@@ -492,7 +492,7 @@ Now all `Player` nodes, regardless of whether they have any `PLAYS_FOR` relation
 
 ====
 
-[role=label--new-2025.06]
+[role=label--new-Neo4j-2025.06 label--cypher-25-only]
 [[conditional-call]]
 == Conditional `CALL` subqueries
 
diff --git a/modules/ROOT/pages/subqueries/collect.adoc b/modules/ROOT/pages/subqueries/collect.adoc
@@ -74,7 +74,7 @@ RETURN person.name as name, COLLECT {
 2+d|Rows: 3
 |===
 
-[role=label--new-2025.06]
+[role=label--new-Neo4j-2025.06 label--cypher-25-only]
 [[conditional-collect]]
 == Conditional `COLLECT` subquery
 
diff --git a/modules/ROOT/pages/subqueries/count.adoc b/modules/ROOT/pages/subqueries/count.adoc
@@ -71,7 +71,7 @@ RETURN person.name AS name
 1+d|Rows: 1
 |===
 
-[role=label--new-2025.06]
+[role=label--new-Neo4j-2025.06 label--cypher-25-only]
 [[conditional-count]]
 == Conditional `COUNT` subquery
 
diff --git a/modules/ROOT/pages/subqueries/existential.adoc b/modules/ROOT/pages/subqueries/existential.adoc
@@ -73,7 +73,7 @@ RETURN person.name AS name
 1+d|Rows: 1
 |===
 
-[role=label--new-2025.06]
+[role=label--new-Neo4j-2025.06 label--cypher-25-only]
 [[conditional-exists]]
 == Conditional `EXISTS` subqueries
 
diff --git a/package-lock.json b/package-lock.json
diff --git a/package.json b/package.json
diff --git a/preview.yml b/preview.yml
diff --git a/publish.yml b/publish.yml
