Add 5.8 documentation for publication (#559)

Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Co-authored-by: Bastien Louërat <[email protected]>
Co-authored-by: Therese Magnusson <[email protected]>
Co-authored-by: Lasse Heemann <[email protected]>

Author: 5 people

modules/ROOT/pages/administration/access-control/dbms-administration.adoc

@@ -1959,6 +1959,8 @@ a|Rows: 2
 [[access-control-dbms-administration-setting]]
 == The DBMS `SETTING` privileges
 
+_This feature was introduced in Neo4j 5.6._
+
 The ability to show configuration settings can be granted via the `SHOW SETTING` privilege.
 A role with this privilege is allowed to query the configuration settings matched by the xref::administration/access-control/dbms-administration.adoc#access-control-name-globbing[name-globbing].
 

modules/ROOT/pages/administration/databases.adoc

@@ -309,7 +309,7 @@ If a user has not been granted `ACCESS` privilege to any databases nor any of th
 ====
 [NOTE]
 ====
-Databases hosted on servers that are offline are also returned by the `SHOW DATABASES` command.
+As of Neo4j 5.3, databases hosted on servers that are offline are also returned by the `SHOW DATABASES` command.
 For such databases, the `address` column displays `NULL`, the `currentStatus` column displays `unknown`, and the `statusMessage` displays `Server is unavailable`.
 ====
 
@@ -1126,6 +1126,8 @@ To ensure the database to be dropped is standard and not composite, the user fir
 [[administration-wait-nowait]]
 == Wait options
 
+_The_ `WAIT` _subclause was added as an option to the_ `ALTER DATABASE` _command in Neo4j 5.7._
+
 Aside from `SHOW DATABASES`, all database management commands accept an optional `WAIT`/`NOWAIT` clause.
 The `WAIT`/`NOWAIT` clause allows you to specify a time limit in which the command must complete and return.
 

modules/ROOT/pages/administration/servers.adoc

@@ -322,6 +322,7 @@ This may not be specified in combination with `allowedDatabases`.
 | tags
 | list of server tags
 | List of server tags used during database allocation and for load balancing and routing policies. 
+label:new[Introduced in 5.6]
 |===
 
 [NOTE]
@@ -368,6 +369,7 @@ This may not be specified in combination with `allowedDatabases`.
 | tags
 | list of server tags
 | List of server tags used during database allocation and for load balancing and routing policies. 
+label:new[Introduced in 5.6]
 |===
 
 [NOTE]
@@ -392,9 +394,12 @@ The new name of the server must be unique.
 [[server-management-reallocate]]
 == Reallocate databases
 
+_The_ `DRYRUN` _feature was introduced in Neo4j 5.2._
+
 After enabling a server, `REALLOCATE DATABASES` can be used to make the cluster re-balance databases across all servers that are part of the cluster.
 Using `DRYRUN REALLOCATE DATABASE` returns a view of how the databases would have been re-balanced if the command was executed without `DRYRUN`:
 
+
 .Result
 [options="header,footer", width="100%", cols="m,m,m,m,m,m"]
 |===
@@ -404,10 +409,6 @@ Using `DRYRUN REALLOCATE DATABASE` returns a view of how the databases would hav
 | "db3"    | "server-1" | "00000000-94ff-4ede-87be-3d741b795480" | "server-5" | "00000003-0df7-4057-81fd-1cf43c9ef5f7" | "primary"
 |===
 
-[NOTE]
-====
-`DRYRUN` is introduced in Neo4j 5.2, and thus is not available in earlier minor releases of v5.
-====
 
 [role=not-on-aura]
 [[server-management-deallocate]]

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

@@ -607,6 +607,9 @@ For larger data sets, you might want to use larger batch sizes, such as `10000 R
 ====
 
 === Error behaviour [[txs_error_behaviour]]
+
+_This feature was introduced in Neo4j 5.7._
+
 Users can choose one of three different option flags to control the behaviour
 in case of an error occurring in any of the inner transactions of `+CALL { ... } IN TRANSACTIONS+`:
 

modules/ROOT/pages/constraints/syntax.adoc

@@ -256,6 +256,7 @@ This is the default if none is given.
 
 |[PROPERTY] UNIQUE[NESS]
 | Returns all property uniqueness constraints, for both nodes and relationships.
+_This feature was introduced in Neo4j 5.3._
 
 |NODE [PROPERTY] EXIST[ENCE]
 | Returns the node property existence constraints.

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

@@ -2288,6 +2288,7 @@ The existing `UNIQUENESS` filter will now return both node and relationship prop
 
 === New features
 
+
 [cols="2", options="header"]
 |===
 | Feature
@@ -2388,6 +2389,25 @@ New privilege that controls a user's access to desired configuration settings.
 [[cypher-deprecations-additions-removals-5.5]]
 == Neo4j 5.5
 
+=== New features
+
+[cols="2", options="header"]
+|===
+| Feature
+| Details
+
+a| 
+label:functionality[]
+label:new[]
+
+New operator: `IntersectionNodeByLabelsScan`
+
+a| 
+The `IntersectionNodeByLabelsScan` operator fetches all nodes that have all of the provided labels from the node label index.
+More information can be found xref::execution-plans/operators.adoc#query-plan-intersection-node-by-labels-scan[here].
+
+|===
+
 === Deprecated features
 
 [cols="2", options="header"]