2025.04 (#1208)

JPryce-Aklundh · web-flow · commit 9cb377436fed · 2025-03-06T13:31:00.000+01:00
diff --git a/antora.yml b/antora.yml
@@ -6,4 +6,4 @@ nav:
 - modules/ROOT/content-nav.adoc
 asciidoc:
   attributes:
-    neo4j-version: '2025.03'
+    neo4j-version: '2025.04'
diff --git a/modules/ROOT/pages/appendix/gql-conformance/index.adoc b/modules/ROOT/pages/appendix/gql-conformance/index.adoc
@@ -2,7 +2,7 @@
 = GQL conformance
 
 *Last updated*: 4 March 2025 +
-*Neo4j version*: 2025.03
+*Neo4j version*: 2025.04
 
 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.03
+:page-role: new-2025.04
 
 `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/load-csv.adoc b/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.03) 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.04) as a replacement for `WITH * WHERE <predicate>`.
 
 .companies.csv
 [source, csv, filename="companies.csv"]
diff --git a/modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc b/modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc
@@ -16,8 +16,8 @@ New features are added to the language continuously, and occasionally, some feat
 This section lists all of the features that have been removed, deprecated, added, or extended in different Cypher versions.
 Replacement syntax for deprecated and removed features are also indicated.
 
-[[cypher-deprecations-additions-removals-2025.03]]
-== Neo4j 2025.03
+[[cypher-deprecations-additions-removals-2025.04]]
+== Neo4j 2025.04
 
 === Removed features
 [cols="2", options="header"]
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 2025.03]
+label:new[Introduced in 2025.04]
 
 1.1+| xref::functions/mathematical-trigonometric.adoc#functions-cot[`cot()`]
 | `cot(input :: FLOAT) :: FLOAT`
@@ -322,7 +322,7 @@ label:new[Introduced in 2025.03]
 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.03]
+label:new[Introduced in 2025.04]
 
 1.1+| xref::functions/mathematical-trigonometric.adoc#functions-degrees[`degrees()`]
 | `degrees(input :: FLOAT) :: FLOAT`
@@ -347,7 +347,7 @@ label:new[Introduced in 2025.03]
 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.03]
+ label:new[Introduced in 2025.04]
 
 1.1+| xref::functions/mathematical-trigonometric.adoc#functions-tan[`tan()`]
 | `tan(input :: FLOAT) :: FLOAT`
@@ -356,7 +356,7 @@ label:new[Introduced in 2025.03]
 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.03]
+label:new[Introduced in 2025.04]
 
 |===
 
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.03]
+[role=label--new-2025.04]
 [[functions-cosh]]
 == cosh()
 
@@ -327,7 +327,7 @@ The cotangent of `0.5` is returned.
 ======
 
 
-[role=label--new-2025.03]
+[role=label--new-2025.04]
 [[functions-coth]]
 == coth()
 
@@ -629,7 +629,7 @@ The sine of `0.5` is returned.
 ======
 
 
-[role=label--new-2025.03]
+[role=label--new-2025.04]
 [[functions-sinh]]
 == sinh()
 
@@ -723,7 +723,7 @@ The tangent of `0.5` is returned.
 
 
 
-[role=label--new-2025.03]
+[role=label--new-2025.04]
 [[functions-tanh]]
 == tanh()
 
diff --git a/modules/ROOT/pages/patterns/shortest-paths.adoc b/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.03, 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.04, 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
diff --git a/modules/ROOT/pages/queries/composed-queries/combined-queries.adoc b/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.03]
+[role=label--new-2025.04]
 [[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.03
+:page-role: new-2025.04
 
 `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
@@ -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.03]
+* xref:queries/composed-queries/conditional-queries.adoc[] label:new[Introduced in Neo4j 2025.04]
diff --git a/modules/ROOT/pages/queries/index.adoc b/modules/ROOT/pages/queries/index.adoc
@@ -8,5 +8,5 @@ It also discusses how to compose combined queries using `UNION` and conditional
 * xref:queries/basic.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.03]
+** xref:queries/composed-queries/conditional-queries.adoc[] label:new[Introduced in Neo4j 2025.04]
 
diff --git a/modules/ROOT/pages/subqueries/call-subquery.adoc b/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.03]
+[role=label--new-2025.04]
 [[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.03]
+[role=label--new-2025.04]
 [[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.03]
+[role=label--new-2025.04]
 [[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.03]
+[role=label--new-2025.04]
 [[conditional-exists]]
 == Conditional `EXISTS` subqueries
 
diff --git a/modules/ROOT/pages/subqueries/subqueries-in-transactions.adoc b/modules/ROOT/pages/subqueries/subqueries-in-transactions.adoc
@@ -749,7 +749,7 @@ RETURN status.transactionId AS transaction, status.committed AS commitStatus, st
 While failed transactions may be more efficiently retried using a link:{neo4j-docs-base-uri}/create-applications[driver], below is an example how failed transactions can be retried within the same Cypher query:
 
 [NOTE]
-The query below uses xref:clauses/filter.adoc#filter-with-where[`FILTER`] (introduced in Neo4j 2025.03) as a replacement for `WITH * WHERE <predicate>`.
+The query below uses xref:clauses/filter.adoc#filter-with-where[`FILTER`] (introduced in Neo4j 2025.04) as a replacement for `WITH * WHERE <predicate>`.
 
 .Query retrying failed transactions
 [source, cypher]
