Graph reference updates for Cypher 25 / Neo4j 2025.06 (targeting base)

.backportrc.json

@@ -0,0 +1,5 @@
+{
+    "repoOwner": "Neo4j",
+    "repoName": "docs-operations",
+    "prTitle": "[Cherry-pick][{{targetBranch}}] {{commitMessages}}"
+  }

.github/workflows/auto-backport.yml

@@ -0,0 +1,30 @@
+name: auto-cherry-pick
+on:
+  pull_request_target:
+    types: ["closed"]
+
+jobs:
+  backport:
+    name: Cherry-pick PR
+    runs-on: [ubuntu-latest]
+    if: |
+      github.event.pull_request.merged == true
+      && contains(github.event.pull_request.labels.*.name, 'auto-cherry-pick')
+      && github.event.action == 'closed'
+    steps:
+      - name: Cherry-pick action
+        uses: sorenlouv/backport-github-action@929f69d04adbc196d982e60f02837b6cc00b3129
+        with:
+          github_token: ${{ secrets.DOCS_AUTO_CP_TOKEN }}
+          auto_backport_label_prefix: auto-cherry-pick-to-
+          add_original_reviewers: false
+
+      - name: Info log
+        if: ${{ success() }}
+        run: cat ~/.backport/backport.info.log
+
+      - name: Debug log
+        if: ${{ failure() }}
+        run: cat ~/.backport/backport.debug.log
+
+

README.adoc

@@ -35,3 +35,34 @@ When you run `npm start`, the project is monitored for updates to asciidoc files
 
 If a change to an asciidoc file is detected the site is automatically rebuilt.
 
+== Enable automatic cherry-picking on a PR
+
+To enable automatic cherry-picking on a PR, add the label `auto-cherry-pick` to it.
+Without it, the responsible GitHub action is not going to be triggered.
+
+To select the target branches you would like to cherry-pick your PR to, add labels of the following structure: `auto-cherry-pick-to-<targetBranch>`.
+For example: `auto-cherry-pick-to-main` to cherry-pick it to the branch `main` or `auto-cherry-pick-to-5.x` for the branch `5.x`.
+You may even add new labels for branches that do not have such a label yet.
+
+The feature is triggered by either merging a PR with the `auto-cherry-pick` label or by adding the `auto-cherry-pick` label to an already closed and merged PR.
+In the latter case, ensure that you first add the labels containing the target branches and then finally the `auto-cherry-pick` label.
+Otherwise the automation starts without any target branches.
+
+=== Details
+
+The PRs created by this GitHub action will have their heading prefixed with `[Cherry-pick][<targetBranch>]`.
+So, for example, for `main` as the target branch and `some changes` as the original PR heading, it results in `[Cherry-pick][main] some changes` as the heading for the cherry-picked PR.
+In case an assignee was set for the original PR, the cherry-picked PRs will also receive the same assignee.
+You must add reviewers manually after the cherry-picked PRs have been created.
+
+The creation of cherry-picked PRs can take a few minutes.
+If you are an assignee of the original PR, you receive an email notification once the cherry-picked PRs have been created.
+The original PR is updated with a comment that contains links to the newly created cherry-picked PRs.
+
+In case of a merge conflict while cherry-picking to a specific release branch, the branch will be skipped.
+Information on skipped branches is also included in the comment added to the original PR.
+In that case you have to take care of cherry-picking manually and resolve the conflicts.
+This is not going to influence the other release branches as long as they do not have conflicts.
+
+
+

antora.yml

@@ -1,14 +1,14 @@
 name: operations-manual
 title: Operations Manual
-version: '2025.04'
+version: '2025.06'
 current: true
 start_page: ROOT:index.adoc
 nav:
 - modules/ROOT/content-nav.adoc
 asciidoc:
   attributes:
-    neo4j-version: '2025.04'
-    neo4j-version-minor: '2025.04'
-    neo4j-version-exact: '2025.04.0'
-    neo4j-buildnumber: '2025.04'
-    neo4j-debian-package-version: '1:2025.04.0@'
+    neo4j-version: '2025.06'
+    neo4j-version-minor: '2025.06'
+    neo4j-version-exact: '2025.06.0'
+    neo4j-buildnumber: '2025.06'
+    neo4j-debian-package-version: '1:2025.06.0@'

models/hospital/access-control-old.adoc

@@ -1,11 +1,11 @@
 [role=enterprise-edition]
 [[auth-access-control]]
 = Fine-grained access control
-:description: Describes an example that illustrates various aspects of security and fine-grained access control. 
+:description: Describes an example that illustrates various aspects of security and fine-grained access control.
 
 When creating a database, administrators may want to establish which users have the ability to access certain information.
 
-As described in xref:authentication-authorization/built-in-roles/auth-built-in-roles[Built-in roles], Neo4j already offers preset roles configured to specific permissions (i.e. read, edit, or write). 
+As described in xref:authentication-authorization/built-in-roles.adoc[Built-in roles], Neo4j already offers preset roles configured to specific permissions (i.e. read, edit, or write).
 While these built-in roles cover many common daily scenarios, it is also possible to create custom roles for specific needs.
 
 This page contains an example that illustrates various aspects of security and fine-grained access control.
@@ -35,7 +35,7 @@ They can be described using the properties:
 * `description`
 
 `(:Disease)`::
-Known illnesses mapped in a catalog found in the database. 
+Known illnesses mapped in a catalog found in the database.
 They can be described using the properties:
 +
 * `name`
@@ -82,10 +82,10 @@ This same database would be used by a number of different users, each with diffe
 
 Unlike applications which often require users to be modeled within the application itself, databases provide user management resources such as roles and privileges.
 This allows users to be created entirely within the database security model, a strategy that allows the separation of access to the data and the data itself.
-For more information, see link:/docs/cypher-manual/{neo4j-version}/access-control/[Cypher Manual -> Access control].
+For more information, see link:{neo4j-docs-base-uri}/cypher-manual/current/access-control/[Cypher Manual -> Access control].
 
 The following examples show two different approaches to using Neo4j security features to support the _healthcare_ database application.
-The first approach uses xref:authentication-authorization/built-in-roles/auth-built-in-roles[Built-in roles], whereas the second uses more advanced resources with fine-grained privileges for <<auth-access-control-using-privileges, sub-graph access control>>.
+The first approach uses xref:authentication-authorization/built-in-roles.adoc[Built-in roles], whereas the second uses more advanced resources with fine-grained privileges for <<auth-access-control-using-privileges, sub-graph access control>>.
 
 In this example, consider five users of the _healthcare_ database:
 
@@ -128,13 +128,13 @@ Neo4j comes with built-in roles that cover a number of common needs:
 * `architect` - Has all the capabilities of the publisher as well as the ability to manage indexes and constraints.
 * `admin` - Can perform architect actions as well as manage databases, users, roles, and privileges.
 
-Consider Charlie from the example of users. 
+Consider Charlie from the example of users.
 As a researcher, they do not need write access to the database, so they are assigned the `reader` role.
 
-On the other hand, Alice (the doctor), Daniel (the nurse), and Bob (the receptionist) all need to update the database with new patient information, but do not need to expand the schema with new labels, relationship types, property names or indexes. 
+On the other hand, Alice (the doctor), Daniel (the nurse), and Bob (the receptionist) all need to update the database with new patient information, but do not need to expand the schema with new labels, relationship types, property names or indexes.
 For this reason, they are all assigned the `editor` role.
 
-Tina, the IT administrator who installs and manages the database, needs to be assigned the `admin` role. 
+Tina, the IT administrator who installs and manages the database, needs to be assigned the `admin` role.
 
 Here is how to grant roles to the users:
 
@@ -183,11 +183,11 @@ Has the permission to save _diagnoses_ to the database, but not expand the schem
 Receptionist::
 Should be able to read and write all patient data, but not be able to see the symptoms, diseases, or diagnoses.
 Researcher::
-Should be able to perform statistical analysis of all data, except patients’ personal information, to which they should have restricted access. 
+Should be able to perform statistical analysis of all data, except patients’ personal information, to which they should have restricted access.
 To illustrate two different ways of setting up the same effective privileges, two roles are created for comparison.
 Nurse::
 Should be able to perform all tasks that both the doctor and the receptionist can do.
-Granting both roles (doctor and receptionist) to the nurse does not work as expected. 
+Granting both roles (doctor and receptionist) to the nurse does not work as expected.
 This is explained in the section dedicated to the creation of the `nurse` role.
 Junior nurse::
 While the senior nurse is able to save diagnoses just as a doctor can, some (junior) nurses might not be allowed to do that.
@@ -278,7 +278,7 @@ SHOW ROLE itadmin PRIVILEGES AS COMMANDS;
 
 [NOTE]
 ====
-Privileges that were granted or denied earlier can be revoked using link:/docs/cypher-manual/{neo4j-version}/access-control/manage-privileges/#access-control-revoke-privileges[the `REVOKE` command].
+Privileges that were granted or denied earlier can be revoked using link:{neo4j-docs-base-uri}/cypher-manual/current/access-control/manage-privileges/#access-control-revoke-privileges[the `REVOKE` command].
 ====
 
 To provide the IT administrator `tina` these privileges, they must be assigned the new role `itadmin`:
@@ -500,7 +500,7 @@ If the `researcherB` role is revoked to Charlie, but `researcherW` is granted, w
 
 [NOTE]
 ====
-Privileges that were granted or denied earlier can be revoked using link:/docs/cypher-manual/{neo4j-version}/access-control/manage-privileges/#access-control-revoke-privileges[the `REVOKE` command].
+Privileges that were granted or denied earlier can be revoked using link:{neo4j-docs-base-uri}/cypher-manual/current/access-control/manage-privileges/#access-control-revoke-privileges[the `REVOKE` command].
 ====
 
 === Privileges of `doctor`
@@ -709,7 +709,7 @@ RETURN n.name, n.ssn, n.address, n.dateOfBirth;
 
 [[detach-delete-restricted-user]]
 
-With the `receptionist` role, Bob can delete any new patient nodes they have just created, but they are not able to delete patients that have already received diagnoses since those are connected to parts of the graph that Bob cannot see. 
+With the `receptionist` role, Bob can delete any new patient nodes they have just created, but they are not able to delete patients that have already received diagnoses since those are connected to parts of the graph that Bob cannot see.
 Here is a demonstration of both scenarios:
 
 [source, cypher]
@@ -787,7 +787,7 @@ GRANT DELETE ON GRAPH healthcare RELATIONSHIPS HAS, DIAGNOSIS TO receptionist;
 
 [NOTE]
 ====
-Privileges that were granted or denied earlier can be revoked using link:/docs/cypher-manual/{neo4j-version}/access-control/manage-privileges/#access-control-revoke-privileges[the `REVOKE` command].
+Privileges that were granted or denied earlier can be revoked using link:{neo4j-docs-base-uri}/cypher-manual/current/access-control/manage-privileges/#access-control-revoke-privileges[the `REVOKE` command].
 ====
 
 === Privileges of nurses
@@ -838,7 +838,7 @@ SHOW USER daniel PRIVILEGES AS COMMANDS;
 
 [NOTE]
 ====
-Privileges that were granted or denied earlier can be revoked using link:/docs/cypher-manual/{neo4j-version}/access-control/manage-privileges/#access-control-revoke-privileges[the `REVOKE` command].
+Privileges that were granted or denied earlier can be revoked using link:{neo4j-docs-base-uri}/cypher-manual/current/access-control/manage-privileges/#access-control-revoke-privileges[the `REVOKE` command].
 ====
 
 Now the intention is that a nurse can perform the actions of a receptionist, which means they should be able to read and write the `address` field of the `Patient` nodes.
@@ -1111,7 +1111,7 @@ neo4j@system> SHOW USER tina PRIVILEGES AS COMMANDS;
 ====
 No other privilege management privileges were granted here.
 How much power this role should have would depend on the requirements of the system.
-Refer to the section link:/docs/cypher-manual/{neo4j-version}/access-control/built-in-roles/[Cypher Manual -> The `admin` role] for a complete list of privileges to consider.
+Refer to the section link:{neo4j-docs-base-uri}/cypher-manual/current/access-control/built-in-roles/[Cypher Manual -> The `admin` role] for a complete list of privileges to consider.
 ====
 
 Now Tina should be able to create new users and assign them to roles:

modules/ROOT/content-nav.adoc

@@ -80,8 +80,11 @@
 ** xref:configuration/ports.adoc[]
 ** xref:configuration/connectors.adoc[]
 ** xref:configuration/set-initial-password.adoc[]
+** xref:configuration/neo4j-admin-memrec.adoc[]
 ** xref:configuration/plugins.adoc[Plugins]
 ** xref:configuration/dynamic-settings.adoc[]
+** xref:configuration/migrate-configuration.adoc[]
+** xref:configuration/validate-config.adoc[]
 ** xref:configuration/configuration-settings.adoc[]
 *** xref:configuration/configuration-settings.adoc#_checkpoint_settings[Checkpoint settings]
 *** xref:configuration/configuration-settings.adoc#_cloud_storage_integration_settings[Cloud storage integration settings]
@@ -103,14 +106,20 @@
 *** xref:configuration/configuration-settings.adoc#_transaction_settings[Transaction settings]
 *** xref:configuration/configuration-settings.adoc#_transaction_log_settings[Transaction log settings]
 
+* xref:import.adoc[]
+
 * xref:database-administration/index.adoc[]
 ** xref:database-administration/syntax.adoc[]
 ** Standard databases
 *** xref:database-administration/standard-databases/naming-databases.adoc[]
 *** xref:database-administration/standard-databases/create-databases.adoc[]
+*** xref:database-administration/standard-databases/seed-from-uri.adoc[]
 *** xref:database-administration/standard-databases/listing-databases.adoc[]
 *** xref:database-administration/standard-databases/alter-databases.adoc[]
+*** xref:database-administration/standard-databases/recreate-database.adoc[]
 *** xref:database-administration/standard-databases/delete-databases.adoc[]
+*** xref:database-administration/standard-databases/migrate-database.adoc[]
+*** xref:database-administration/standard-databases/upload-to-aura.adoc[]
 *** xref:database-administration/standard-databases/wait-options.adoc[]
 *** xref:database-administration/standard-databases/configuration-parameters.adoc[]
 *** xref:database-administration/standard-databases/errors.adoc[]
@@ -134,6 +143,7 @@
 ** xref:database-internals/transaction-logs.adoc[]
 ** xref:database-internals/checkpointing.adoc[]
 ** xref:database-internals/store-formats.adoc[]
+** xref:database-internals/neo4j-admin-store-info.adoc[]
 
 * xref:clustering/index.adoc[]
 ** xref:clustering/introduction.adoc[]
@@ -157,6 +167,7 @@
 ** xref:clustering/server-syntax.adoc[]
 ** xref:clustering/clustering-advanced/index.adoc[]
 *** xref:clustering/clustering-advanced/default-database.adoc[]
+*** xref:clustering/clustering-advanced/unbind.adoc[]
 *** xref:clustering/clustering-advanced/multi-data-center-routing.adoc[]
 *** xref:clustering/clustering-advanced/reconciler.adoc[]
 ** xref:clustering/glossary.adoc[]
@@ -167,6 +178,7 @@
 ** xref:backup-restore/online-backup.adoc[]
 ** xref:backup-restore/aggregate.adoc[]
 ** xref:backup-restore/inspect.adoc[]
+** xref:backup-restore/consistency-checker.adoc[]
 ** xref:backup-restore/restore-backup.adoc[]
 ** xref:backup-restore/offline-backup.adoc[]
 ** xref:backup-restore/restore-dump.adoc[]
@@ -202,6 +214,7 @@
 
 * xref:performance/index.adoc[]
 ** xref:performance/memory-configuration.adoc[]
+** xref:performance/vector-index-memory-configuration.adoc[]
 ** xref:performance/index-configuration.adoc[]
 ** xref:performance/gc-tuning.adoc[]
 ** xref:performance/bolt-thread-pool-configuration.adoc[]
@@ -220,23 +233,13 @@
 ** xref:monitoring/query-management.adoc[]
 ** xref:monitoring/connection-management.adoc[]
 ** xref:monitoring/background-jobs.adoc[]
+** xref:monitoring/neo4j-admin-report.adoc[]
 // ** xref:monitoring/cluster/index.adoc[]
 // *** xref:monitoring/cluster/procedures.adoc[]
 // *** xref:monitoring/cluster/http-endpoints.adoc[]
 
-* xref:tools/index.adoc[]
-** xref:tools/neo4j-admin/index.adoc[]
-*** xref:tools/neo4j-admin/consistency-checker.adoc[]
-*** xref:tools/neo4j-admin/neo4j-admin-report.adoc[]
-*** xref:tools/neo4j-admin/neo4j-admin-store-info.adoc[]
-*** xref:tools/neo4j-admin/neo4j-admin-memrec.adoc[]
-*** xref:tools/neo4j-admin/neo4j-admin-import.adoc[]
-*** xref:tools/neo4j-admin/unbind.adoc[]
-*** xref:tools/neo4j-admin/upload-to-aura.adoc[]
-*** xref:tools/neo4j-admin/migrate-database.adoc[]
-*** xref:tools/neo4j-admin/migrate-configuration.adoc[]
-*** xref:tools/neo4j-admin/validate-config.adoc[]
-** xref:tools/cypher-shell.adoc[]
+* xref:neo4j-admin-neo4j-cli.adoc[]
+* xref:cypher-shell.adoc[]
 
 * xref:procedures.adoc[]