Cypher 25: Remove 5.x "Introduced in" labels and in-text notifications (#1056)

Author: JPryce-Aklundh

modules/ROOT/pages/appendix/tutorials/advanced-query-tuning.adoc

@@ -939,7 +939,7 @@ Predicates that will not work:
 If there is an existence constraint on the property, no predicate is required to trigger the optimization.
 For example, `CREATE CONSTRAINT constraint_name FOR (p:Person) REQUIRE p.name IS NOT NULL`
 
-As of Neo4j {neo4j-version-exact}, predicates with parameters, such as `WHERE n.prop > $param`, can trigger _index-backed ORDER BY_.
+Predicates with parameters, such as `WHERE n.prop > $param`, can trigger _index-backed ORDER BY_.
 The only exception are queries with parameters of type `POINT`.
 ====
 

modules/ROOT/pages/clauses/call.adoc

@@ -259,7 +259,7 @@ A `VOID` procedure is a procedure that does not declare any result fields and re
 `VOID` procedure only produces side-effects and does not allow for the use of `YIELD`.
 Calling a `VOID` procedure in the middle of a larger query will simply pass on each input record (i.e., it acts like xref:clauses/with.adoc[`WITH *`] in terms of the record stream).
 
-[role=label--new-5.24]
+
 [[optional-call]]
 == Optional procedure calls
 

modules/ROOT/pages/clauses/clause-composition.adoc

@@ -573,8 +573,7 @@ Later invocations of the subquery can observe writes made by earlier invocations
 Using the same example graph as above, this example shows the table of intermediate results and the state of the graph after each clause for the following query:
 
 [NOTE]
-The below query uses a xref:subqueries/call-subquery.adoc#variable-scope-clause[variable scope clause] (introduced in Neo4j 5.23) to import variables into the `CALL` subquery.
-If you are using an older version of Neo4j, use an xref:subqueries/call-subquery.adoc#importing-with[importing `WITH` clause] instead.
+The below query uses a xref:subqueries/call-subquery.adoc#variable-scope-clause[variable scope clause] to import variables into the `CALL` subquery.
 
 [source,cypher]
 ----

modules/ROOT/pages/clauses/create.adoc

@@ -23,7 +23,7 @@ Multiple labels are separated by colons.
 CREATE (charlie:Person:Actor {name: 'Charlie Sheen'}), (oliver:Person:Director {name: 'Oliver Stone'})
 ----
 
-As of Neo4j 5.18, multiple labels can also be separated by an ampersand `&`, in the same manner as it is used in xref:patterns/reference.adoc#label-expressions[label expressions].
+Multiple labels can also be separated by an ampersand `&`, in the same manner as it is used in xref:patterns/reference.adoc#label-expressions[label expressions].
 Separation by colon `:` and ampersand `&` cannot be mixed in the same clause.
 
 .Query
@@ -205,7 +205,7 @@ Nodes created: 2 +
 Properties set: 4
 |===
 
-[role=label--new-5.18]
+
 [[insert-as-synonym-of-create]]
 == `INSERT` as a synonym of `CREATE`
 

modules/ROOT/pages/clauses/delete.adoc

@@ -58,7 +58,7 @@ This query is only possible to run on nodes without any relationships connected
 Deleted 1 node
 ----
 
-[role=label--new-5.14]
+
 [[delete-nodetach]]
 === NODETACH keyword
 

modules/ROOT/pages/clauses/finish.adoc

@@ -1,5 +1,4 @@
 :description: The `FINISH` clause defines a query to have no result.
-:page-role: new-5.19
 [[query-finish]]
 = FINISH
 

modules/ROOT/pages/clauses/index.adoc

@@ -63,15 +63,12 @@ m| xref::clauses/where.adoc[WHERE]
 
 m| xref::clauses/order-by.adoc[ORDER BY [ASC[ENDING\] \| DESC[ENDING\]\]]
 | A sub-clause following `RETURN` or `WITH`, specifying that the output should be sorted in either ascending (the default) or descending order.
-As of Neo4j 5.24, it can also be used as a standalone clause.
 
 m| xref::clauses/skip.adoc[SKIP] / xref::clauses/skip.adoc#offset-synonym[`OFFSET`]
 | Defines from which row to start including the rows in the output.
-As of Neo4j 5.24, it can be used as a standalone clause.
 
 m| xref::clauses/limit.adoc[LIMIT]
 | Constrains the number of rows in the output.
-As of Neo4j 5.24, it can be used as a standalone clause.
 
 |===
 

modules/ROOT/pages/clauses/limit.adoc

@@ -159,7 +159,7 @@ d|Rows: 1 +
 Properties set: 1
 |===
 
-[role=label--new-5.24]
+
 [[limit-standalone-clause]]
 == Using `LIMIT` as a standalone clause
 

modules/ROOT/pages/clauses/listing-functions.adoc

@@ -66,12 +66,12 @@ m| LIST<STRING>
 
 m| isDeprecated
 a| Whether the function is deprecated.
-label:new[Introduced in 5.9]
+
 m| BOOLEAN
 
 m| deprecatedBy
 a| The replacement function to use in case of deprecation; otherwise `null`.
-label:new[Introduced in 5.21]
+
 m| STRING
 
 |===

modules/ROOT/pages/clauses/listing-procedures.adoc

@@ -64,12 +64,12 @@ m| LIST<STRING>
 
 m| isDeprecated
 a| Whether the procedure is deprecated.
-label:new[Introduced in 5.9]
+
 m| BOOLEAN
 
 m| deprecatedBy
 a| The replacement procedure to use in case of deprecation; otherwise `null`.
-label:new[Introduced in 5.21]
+
 m| STRING
 
 m| option