2025.01 publish

antora.yml

@@ -6,6 +6,4 @@ nav:
 - modules/ROOT/content-nav.adoc
 asciidoc:
   attributes:
-    neo4j-version: '5'
-    neo4j-version-minor: '5.26'
-    neo4j-version-exact: '5.26.0'
+    neo4j-version: '2025.01'

modules/ROOT/pages/administration/index.adoc

@@ -1,6 +1,6 @@
 = Administration
 
-The pages previously in this chapter have been moved to the link:{neo4j-docs-base-uri}/operations-manual/{page-version}/[Operations Manual].
+The pages previously in this chapter have been moved to the link:{neo4j-docs-base-uri}/operations-manual/current/[Operations Manual].
 
 More specific information about the content relocation is listed in the table:
 
@@ -9,13 +9,13 @@ More specific information about the content relocation is listed in the table:
 
 | Content | New location in Operations Manual 
 
-| Database management | link:{neo4j-docs-base-uri}/operations-manual/{page-version}/database-administration/[Database administration]
+| Database management | link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/[Database administration]
 
-| Alias management | link:{neo4j-docs-base-uri}/operations-manual/{page-version}/database-administration/aliases/manage-aliases-standard-databases/[Managing aliases]
+| Alias management | link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/aliases/manage-aliases-standard-databases/[Managing aliases]
 
-| Server management | link:{neo4j-docs-base-uri}/operations-manual/{page-version}/clustering/[Managing servers in a cluster]
+| Server management | link:{neo4j-docs-base-uri}/operations-manual/current/clustering/[Managing servers in a cluster]
 
-| Access control | link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/[Authentication and authorization]
+| Access control | link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/[Authentication and authorization]
 
 |===
 

modules/ROOT/pages/appendix/gql-conformance/additional-cypher.adoc

@@ -208,7 +208,7 @@ REMOVE n:$($label)
 | xref:functions/graph.adoc#functions-graph-by-elementid[`graph.byElementId()`]
 | Returns the graph reference with the given element id. 
 It is only supported in the xref:clauses/use.adoc[`USE`] clause.
-As of Neo4j 5.26, it is supported on both link:{neo4j-docs-base-uri}/operations-manual/{page-version}/database-administration/[standard and composite databases].
+As of Neo4j 5.26, it is supported on both link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/[standard and composite databases].
 On earlier versions, it is only supported on composite databases.
 
 | xref:functions/graph.adoc#functions-graph-byname[`graph.byName()`]
@@ -658,23 +658,23 @@ For more information, see xref:planning-and-tuning/query-tuning.adoc[Query optio
 == Administration
 
 [NOTE]
-The documentation for Cypher's administration commands is located in Neo4j's link:{neo4j-docs-base-uri}/operations-manual/{page-version}/[Operation Manual].
+The documentation for Cypher's administration commands is located in Neo4j's link:{neo4j-docs-base-uri}/operations-manual/current/[Operation Manual].
 
 [options="header", cols="2a,5a"]
 |===
 | Cypher feature
 | Description
 
-| link:{neo4j-docs-base-uri}/operations-manual/{page-version}/database-administration/[Database management]
+| link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/[Database management]
 | Commands to `CREATE`, `SHOW`, `ALTER`, and `DROP` standard and composite databases.
 
-| link:{neo4j-docs-base-uri}/operations-manual/{page-version}/database-administration/aliases/manage-aliases-standard-databases/[Alias management]
+| link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/aliases/manage-aliases-standard-databases/[Alias management]
 | Commands to `CREATE`, `SHOW`, `ALTER`, and `DROP` database aliases.
 
-| link:{neo4j-docs-base-uri}/operations-manual/{page-version}/clustering/[Server management]
+| link:{neo4j-docs-base-uri}/operations-manual/current/clustering/[Server management]
 | Commands to administer servers in a cluster and the databases allocated to them.
 
-| link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/[Authentication and authorization]
+| link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/[Authentication and authorization]
 | Commands to manage users, roles, and privileges.
 
 |===

modules/ROOT/pages/appendix/gql-conformance/supported-mandatory.adoc

@@ -155,7 +155,7 @@ This is currently not available in Cypher.
 | <value specification>
 | 
 | GQL defines the `SESSION_USER` value expression, which enables accessing a user’s username within a query.
-In Cypher, current user details can be seen using the link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/manage-users/#access-control-current-users[`SHOW CURRENT USER` command].
+In Cypher, current user details can be seen using the link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/manage-users/#access-control-current-users[`SHOW CURRENT USER` command].
 
 | 20.7
 | <case expression>

modules/ROOT/pages/appendix/gql-conformance/unsupported-mandatory.adoc

@@ -28,7 +28,7 @@ Neo4j offers session management through the link:{neo4j-docs-base-uri}/create-ap
 | GQL defines the following transaction commands: `START TRANSACTION`, `COMMIT`, and `ROLLBACK`.
 
 Neo4j offers transaction management through the link:{neo4j-docs-base-uri}/create-applications[driver] transaction API.
-Cypher Shell also offers specific link:{neo4j-docs-base-uri}/operations-manual/{page-version}/tools/cypher-shell/#cypher-shell-commands[commands] to manage transactions.
+Cypher Shell also offers specific link:{neo4j-docs-base-uri}/operations-manual/current/tools/cypher-shell/#cypher-shell-commands[commands] to manage transactions.
 
 | 11.1
 | Graph expressions

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

@@ -16,7 +16,7 @@ Let's explain how to use these features with a more advanced query tuning exampl
 [NOTE]
 ====
 If you are upgrading an existing store, it may be necessary to drop and re-create existing indexes.
-For information on native index support and upgrade considerations regarding indexes, see link:{neo4j-docs-base-uri}/operations-manual/{page-version}/performance/index-configuration[Operations Manual -> Performance -> Index configuration].
+For information on native index support and upgrade considerations regarding indexes, see link:{neo4j-docs-base-uri}/operations-manual/current/performance/index-configuration[Operations Manual -> Performance -> Index configuration].
 ====
 
 
@@ -540,8 +540,8 @@ It assumes that your current work directory is the _<neo4j-home>_ directory of t
 
 [NOTE]
 ====
-* For the default directory of other installations see, link:{neo4j-docs-base-uri}/operations-manual/{page-version}/configuration/file-locations[Operations Manual -> File locations].
-* The import location can be configured with link:{neo4j-docs-base-uri}/operations-manual/{page-version}/configuration/configuration-settings#config_server.directories.import[Operations Manual -> `server.directories.import`].
+* For the default directory of other installations see, link:{neo4j-docs-base-uri}/operations-manual/current/configuration/file-locations[Operations Manual -> File locations].
+* The import location can be configured with link:{neo4j-docs-base-uri}/operations-manual/current/configuration/configuration-settings#config_server.directories.import[Operations Manual -> `server.directories.import`].
 ====
 
 == Importing the data
@@ -669,7 +669,7 @@ Planner COST
 
 Runtime PIPELINED
 
-Runtime version {neo4j-version-minor}
+Runtime version {neo4j-version}
 
 Batch size 128
 
@@ -711,7 +711,7 @@ Planner COST
 
 Runtime PIPELINED
 
-Runtime version {neo4j-version-minor}
+Runtime version {neo4j-version}
 
 Batch size 128
 
@@ -776,7 +776,7 @@ Planner COST
 
 Runtime PIPELINED
 
-Runtime version {neo4j-version-minor}
+Runtime version {neo4j-version}
 
 Batch size 128
 
@@ -823,7 +823,7 @@ Planner COST
 
 Runtime PIPELINED
 
-Runtime version {neo4j-version-minor}
+Runtime version {neo4j-version}
 
 Batch size 128
 
@@ -878,7 +878,7 @@ Planner COST
 
 Runtime PIPELINED
 
-Runtime version {neo4j-version-minor}
+Runtime version {neo4j-version}
 
 Batch size 128
 

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

@@ -525,8 +525,8 @@ It assumes that your current work directory is the _<neo4j-home>_ directory of t
 
 [NOTE]
 ====
-* For the default directory of other installations see, link:{neo4j-docs-base-uri}/operations-manual/{page-version}/configuration/file-locations[Operations Manual -> File locations].
-* The import location can be configured with link:{neo4j-docs-base-uri}/operations-manual/{page-version}/configuration/configuration-settings#config_server.directories.import[Operations Manual -> `server.directories.import`].
+* For the default directory of other installations see, link:{neo4j-docs-base-uri}/operations-manual/current/configuration/file-locations[Operations Manual -> File locations].
+* The import location can be configured with link:{neo4j-docs-base-uri}/operations-manual/current/configuration/configuration-settings#config_server.directories.import[Operations Manual -> `server.directories.import`].
 ====
 
 == Importing the data
@@ -623,7 +623,7 @@ Planner COST
 
 Runtime PIPELINED
 
-Runtime version {neo4j-version-minor}
+Runtime version {neo4j-version}
 
 Batch size 128
 
@@ -680,7 +680,7 @@ Planner COST
 
 Runtime PIPELINED
 
-Runtime version {neo4j-version-minor}
+Runtime version {neo4j-version}
 
 Batch size 128
 
@@ -747,7 +747,7 @@ Planner COST
 
 Runtime PIPELINED
 
-Runtime version {neo4j-version-minor}
+Runtime version {neo4j-version}
 
 Batch size 128
 

modules/ROOT/pages/appendix/tutorials/shortestpath-planning.adoc

@@ -20,7 +20,7 @@ When the exhaustive search is planned, it is still only executed when the fast a
 The fast algorithm is always executed first, since it is possible that it can find a valid path even though that could not be guaranteed at planning time.
 
 Please note that falling back to the exhaustive search may prove to be a very time consuming strategy in some cases; such as when there is no shortest path between two nodes.
-Therefore, in these cases, it is recommended to set `cypher.forbid_exhaustive_shortestpath` to `true`, as explained in link:{neo4j-docs-base-uri}/operations-manual/{page-version}/configuration/configuration-settings#config_dbms.cypher.forbid_exhaustive_shortestpath[Operations Manual -> Configuration settings].
+Therefore, in these cases, it is recommended to set `cypher.forbid_exhaustive_shortestpath` to `true`, as explained in link:{neo4j-docs-base-uri}/operations-manual/current/configuration/configuration-settings#config_dbms.cypher.forbid_exhaustive_shortestpath[Operations Manual -> Configuration settings].
 
 
 == Shortest path -- fast algorithm
@@ -81,7 +81,7 @@ Planner COST
 
 Runtime PIPELINED
 
-Runtime version {neo4j-version-minor}
+Runtime version {neo4j-version}
 
 Batch size 128
 
@@ -158,7 +158,7 @@ Planner COST
 
 Runtime PIPELINED
 
-Runtime version {neo4j-version-minor}
+Runtime version {neo4j-version}
 
 Batch size 1024
 
@@ -261,7 +261,7 @@ Planner COST
 
 Runtime PIPELINED
 
-Runtime version {neo4j-version-minor}
+Runtime version {neo4j-version}
 
 Batch size 128
 

modules/ROOT/pages/clauses/call.adoc

@@ -12,9 +12,9 @@ For information about how to list procedures, see xref:clauses/listing-procedure
 
 [NOTE]
 Neo4j comes with a number of built-in procedures.
-For a list of these, see link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/procedures[Operations Manual -> Procedures].
+For a list of these, see link:{neo4j-docs-base-uri}/operations-manual/current/reference/procedures[Operations Manual -> Procedures].
 Users can also develop custom procedures and deploy to the database.
-See link:{neo4j-docs-base-uri}/java-reference/{page-version}/extending-neo4j/procedures#extending-neo4j-procedures[Java Reference -> User-defined procedures] for details.
+See link:{neo4j-docs-base-uri}/java-reference/current/extending-neo4j/procedures#extending-neo4j-procedures[Java Reference -> User-defined procedures] for details.
 
 [[example-graph]]
 == Example graph
@@ -42,7 +42,7 @@ CREATE (andy:Developer {name: 'Andy', born: 1991}),
 .`CALL` a procedure without arguments
 ====
 
-This example calls the built-in procedure link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/procedures/#procedure_db_labels[`db.labels()`], which lists all labels used in the database.
+This example calls the built-in procedure link:{neo4j-docs-base-uri}/operations-manual/current/reference/procedures/#procedure_db_labels[`db.labels()`], which lists all labels used in the database.
 
 .Query
 [source, cypher]
@@ -72,7 +72,7 @@ Omission of parentheses is available only in a so-called standalone procedure ca
 ====
 
 
-This example calls the procedure link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/procedures/#procedure_dbms_checkconfigvalue[`dbms.checkConfigValue()`], which checks the validity of a configuration setting value, using literal arguments.
+This example calls the procedure link:{neo4j-docs-base-uri}/operations-manual/current/reference/procedures/#procedure_dbms_checkconfigvalue[`dbms.checkConfigValue()`], which checks the validity of a configuration setting value, using literal arguments.
 
 .Query
 [source, cypher]
@@ -206,7 +206,7 @@ RETURN count(*) AS results
 ====
 
 `YIELD` can be used to filter for specific results.
-This requires knowing the names of the arguments within a procedure's signature, which can either be found in the link:{neo4j-docs-base-uri}/operations-manual/{page-version}/reference/procedures/[Operations Manual -> Procedures] or in the `signature` column returned by a `SHOW PROCEDURES` command (see example below).
+This requires knowing the names of the arguments within a procedure's signature, which can either be found in the link:{neo4j-docs-base-uri}/operations-manual/current/reference/procedures/[Operations Manual -> Procedures] or in the `signature` column returned by a `SHOW PROCEDURES` command (see example below).
 
 .Find the argument names of `db.propertyKeys`
 [source, cypher]
@@ -271,7 +271,7 @@ Similar to xref:clauses/optional-match.adoc[`OPTIONAL MATCH`] any empty rows pro
 .Difference between using `CALL` and `OPTIONAL CALL`
 ====
 
-This query uses the link:{neo4j-docs-base-uri}/apoc/{page-version}/overview/apoc.neighbors/apoc.neighbors.tohop[`apoc.neighbors.tohop()`] procedure (part of Neo4j's link:{neo4j-docs-base-uri}/apoc/{page-version}/[APOC Core library]), which returns all nodes connected by the given relationship type within the specified distance (1 hop, in this case) and direction.
+This query uses the link:{neo4j-docs-base-uri}/apoc/current/overview/apoc.neighbors/apoc.neighbors.tohop[`apoc.neighbors.tohop()`] procedure (part of Neo4j's link:{neo4j-docs-base-uri}/apoc/current/[APOC Core library]), which returns all nodes connected by the given relationship type within the specified distance (1 hop, in this case) and direction.
 
 .Regular procedure `CALL`
 [source, cypher]

modules/ROOT/pages/clauses/delete.adoc

@@ -13,7 +13,7 @@ This can be done by either explicitly deleting specific relationships, or by usi
 
 [NOTE]
 While the `DELETE` clause renders the deleted objects no longer accessible, the space occupied by the deleted nodes and relationships remain on the disk and is reserved for future transactions creating data.
-For information about how to clear and reuse the space occupied by deleted objects, see link:{neo4j-docs-base-uri}/operations-manual/{page-version}/performance/space-reuse/[Operations Manual -> Space reuse].
+For information about how to clear and reuse the space occupied by deleted objects, see link:{neo4j-docs-base-uri}/operations-manual/current/performance/space-reuse/[Operations Manual -> Space reuse].
 
 == Example graph 
 
@@ -120,7 +120,7 @@ Deleted 1 node, deleted 1 relationship
 [NOTE]
 ====
 The `DETACH DELETE` clause may not be permitted to users with restricted security privileges. 
-For more information, see link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/access-control#detach-delete-restricted-user[Operations Manual -> Fine-grained access control].
+For more information, see link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/access-control#detach-delete-restricted-user[Operations Manual -> Fine-grained access control].
 ====
 
 

modules/ROOT/pages/clauses/index.adoc

@@ -282,6 +282,6 @@ m| xref::constraints/syntax.adoc[CREATE \| SHOW \| DROP CONSTRAINT]
 Cypher includes commands to manage databases, aliases, servers, and role-based access control.
 To learn more about each of these, see:
 
-* link:{neo4j-docs-base-uri}/operations-manual/{page-version}/database-administration[Operations Manual -> Database administration]
-* link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/[Operations Manual -> Authentication and authorization]
-* link:{neo4j-docs-base-uri}/operations-manual/{page-version}/clustering/[Operations Manual -> Clustering]
+* link:{neo4j-docs-base-uri}/operations-manual/current/database-administration[Operations Manual -> Database administration]
+* link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/[Operations Manual -> Authentication and authorization]
+* link:{neo4j-docs-base-uri}/operations-manual/current/clustering/[Operations Manual -> Clustering]

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

@@ -55,13 +55,13 @@ m| BOOLEAN
 m| rolesExecution
 a|
 List of roles permitted to execute this function.
-Is `null` without the link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/dbms-administration#access-control-dbms-administration-role-management[`SHOW ROLE`] privilege.
+Is `null` without the link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/dbms-administration#access-control-dbms-administration-role-management[`SHOW ROLE`] privilege.
 m| LIST<STRING>
 
 m| rolesBoostedExecution
 a|
 List of roles permitted to use boosted mode when executing this function.
-Is `null` without the link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/dbms-administration#access-control-dbms-administration-role-management[`SHOW ROLE`] privilege.
+Is `null` without the link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/dbms-administration#access-control-dbms-administration-role-management[`SHOW ROLE`] privilege.
 m| LIST<STRING>
 
 m| isDeprecated
@@ -81,7 +81,7 @@ m| STRING
 
 [NOTE]
 ====
-More details about the syntax descriptions can be found link:{neo4j-docs-base-uri}/operations-manual/{page-version}/database-administration/syntax/#administration-syntax-reading[here].
+More details about the syntax descriptions can be found link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/syntax/#administration-syntax-reading[here].
 ====
 
 List functions, either all or only built-in or user-defined::
@@ -124,7 +124,7 @@ SHOW [ALL|BUILT IN|USER DEFINED] FUNCTION[S] EXECUTABLE BY username
 [RETURN field[, ...] [ORDER BY field[, ...]] [SKIP n] [LIMIT n]]
 ----
 
-Required privilege link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/dbms-administration#access-control-dbms-administration-user-management[`SHOW USER`].
+Required privilege link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/dbms-administration#access-control-dbms-administration-user-management[`SHOW USER`].
 This command cannot be used for LDAP users.
 
 [NOTE]
@@ -363,7 +363,7 @@ SHOW FUNCTIONS EXECUTABLE BY CURRENT USER YIELD *
 6+d|Rows: 10
 |===
 
-Notice that the two `roles` columns are empty due to missing the link:{neo4j-docs-base-uri}/operations-manual/{page-version}/authentication-authorization/dbms-administration#access-control-dbms-administration-role-management[`SHOW ROLE`] privilege.
+Notice that the two `roles` columns are empty due to missing the link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/dbms-administration#access-control-dbms-administration-role-management[`SHOW ROLE`] privilege.
 Also note that the following columns are not present in the table: 
 
 * `signature`