Remove all introduced in 5.x mentions from the dev branch

Author: renetapopova

modules/ROOT/pages/authentication-authorization/dbms-administration.adoc

@@ -469,7 +469,7 @@ GRANT [IMMUTABLE] SET PASSWORD[S]
 GRANT [IMMUTABLE] SET AUTH
   ON DBMS
   TO role[, ...]
-| label:new[Introduced in 5.24] Enables the specified roles to `SET` or `REMOVE` users' xref:authentication-authorization/auth-providers.adoc[auth providers].
+| Enables the specified roles to `SET` or `REMOVE` users' xref:authentication-authorization/auth-providers.adoc[auth providers].
 
 | [source, syntax, role=noheader]
 GRANT [IMMUTABLE] SET USER HOME DATABASE
@@ -614,7 +614,7 @@ A user that is granted the `SET PASSWORDS` privilege is allowed to run the `ALTE
 ALTER USER jake SET PASSWORD 'abcd5678' CHANGE NOT REQUIRED
 ----
 
-label:new[Introduced in 5.24] A user that is granted the `SET AUTH` privilege is allowed to run the `ALTER USER` administration command with one or both of the `SET AUTH` and `REMOVE AUTH` parts:
+A user that is granted the `SET AUTH` privilege is allowed to run the `ALTER USER` administration command with one or both of the `SET AUTH` and `REMOVE AUTH` parts:
 
 [source, cypher, role=noplay]
 ----
@@ -1926,7 +1926,7 @@ a|Rows: 2
 ======
 
 
-[role=label--new-5.6]
+
 [[access-control-dbms-administration-setting]]
 == The DBMS `SETTING` privileges
 

modules/ROOT/pages/authentication-authorization/ldap-integration.adoc

@@ -334,7 +334,7 @@ dbms.security.ldap.authorization.access_permitted_group=501
 . Map the groups in the LDAP system to the Neo4j built-in and custom roles.
 For more information, see xref:authentication-authorization/ldap-integration.adoc#auth-ldap-map-ldap-roles[Map the LDAP groups to the Neo4j roles].
 
-[role=label--new-5.24]
+[role=]
 [[auth-ldap-auth-providers]]
 == Configure authentication/authorization at the user level using auth providers
 xref:authentication-authorization/auth-providers.adoc[User auth providers] can be used to determine which users can authenticate and authorize using the configured providers, including LDAP.

modules/ROOT/pages/authentication-authorization/load-privileges.adoc

@@ -46,8 +46,7 @@ GRANT [IMMUTABLE] LOAD
 GRANT [IMMUTABLE] LOAD
   ON CIDR cidr
   TO role[, ...]
-| Enables the specified roles to load external data from the given CIDR range in queries.label:new[Introduced in 5.16]
-
+| Enables the specified roles to load external data from the given CIDR range in queries.
 |===
 
 [NOTE]

modules/ROOT/pages/authentication-authorization/manage-privileges.adoc

@@ -203,7 +203,7 @@ The following image shows the hierarchy between different graph privileges:
 image::privileges_hierarchy.svg[title="Graph privileges hierarchy"]
 
 
-[role=label--new-5.9]
+
 [[access-control-list-supported-privileges]]
 == Listing supported privileges
 

modules/ROOT/pages/authentication-authorization/manage-users.adoc

@@ -152,7 +152,7 @@ CREATE USER name [IF NOT EXISTS]
   [[SET PASSWORD] CHANGE [NOT] REQUIRED]
   [SET STATUS {ACTIVE \| SUSPENDED}]
   [SET HOME DATABASE name]
-  [SET AUTH [PROVIDER] 'provider' "{"{SET <key> <value>}..."}"]... # Introduced in Neo4j 5.24
+  [SET AUTH [PROVIDER] 'provider' "{"{SET <key> <value>}..."}"]...
 ----
 
 `<key><value>` pairs for the `SET AUTH` clause could include:
@@ -203,7 +203,7 @@ CREATE OR REPLACE USER name
   [[SET PASSWORD] CHANGE [NOT] REQUIRED]
   [SET STATUS {ACTIVE \| SUSPENDED}]
   [SET HOME DATABASE name]
-  [SET AUTH [PROVIDER] 'provider' "{"{SET <key> <value>}..."}"]... # Introduced in Neo4j 5.24
+  [SET AUTH [PROVIDER] 'provider' "{"{SET <key> <value>}..."}"]...
 ----
 `<key><value>` pairs for the `SET AUTH` clause could include:
 [source, syntax, role="noheader"]
@@ -292,7 +292,7 @@ ALTER USER name [IF EXISTS]
   [[SET PASSWORD] CHANGE [NOT] REQUIRED]
   [SET STATUS {ACTIVE \| SUSPENDED} ]
   [SET HOME DATABASE name]
-  [SET AUTH [PROVIDER] 'provider' "{"{SET <key> <value>}..."}"]... # Introduced in Neo4j 5.24
+  [SET AUTH [PROVIDER] 'provider' "{"{SET <key> <value>}..."}"]...
 ----
 `<key><value>` pairs for the `SET AUTH` clause could include:
 [source, syntax, role="noheader"]
@@ -633,7 +633,7 @@ RETURN user AS adminUser
 |===
 ======
 
-[role=label--new-5.24]
+[role=]
 [[access-control-list-user-auth-providers]]
 == Listing user auth providers
 
@@ -801,7 +801,7 @@ If not set, the default is `ACTIVE`.
 A home database is resolved if it is pointing to a database or a database alias.
 If no home database is set, the DBMS default database is used as the home database for that user.
 
-<6> label:new[Introduced in 5.24] One or more `SET AUTH` clause can be used to configure external xref:authentication-authorization/auth-providers.adoc[auth providers], such as LDAP or OIDC, which define authentication/authorization providers for that user.
+<6> One or more `SET AUTH` clause can be used to configure external xref:authentication-authorization/auth-providers.adoc[auth providers], such as LDAP or OIDC, which define authentication/authorization providers for that user.
 `SET AUTH` can also be used as an alternative way to set the native (password-based) auth settings like `SET PASSWORD` and `SET PASSWORD CHANGE REQUIRED`.
 For further informations, see the examples in this section, as well as xref:authentication-authorization/sso-integration.adoc#auth-sso-auth-providers[Configure SSO at the user level using auth providers] for OIDC, and xref:authentication-authorization/ldap-integration.adoc#auth-ldap-auth-providers[Configure authentication/authorization at the user level using auth providers] for LDAP.
 +
@@ -838,7 +838,7 @@ SET STATUS SUSPENDED
 SET HOME DATABASE anotherDb
 ----
 
-[role=label--new-5.24]
+[role=]
 The equivalent command using the xref:authentication-authorization/auth-providers.adoc[auth providers] syntax would be:
 
 [source,cypher,role=noplay]
@@ -862,7 +862,7 @@ SET ENCRYPTED PASSWORD '1,6d57a5e0b3317055454e455f96c98c750c77fb371f3f0634a1b8ff
 SET STATUS ACTIVE
 ----
 
-[role=label--new-5.24]
+[role=]
 The equivalent command using the xref:authentication-authorization/auth-providers.adoc[auth providers] syntax would be:
 .
 [source,cypher,role=noplay]
@@ -896,7 +896,7 @@ CREATE USER jake IF NOT EXISTS
 SET PLAINTEXT PASSWORD 'abcd1234'
 ----
 
-[role=label--new-5.24]
+[role=]
 The equivalent command using the xref:authentication-authorization/auth-providers.adoc[auth providers] syntax would be:
 
 [source,cypher,role=noplay]
@@ -919,7 +919,7 @@ SET PLAINTEXT PASSWORD 'abcd1234'
 
 This is equivalent to running `DROP USER jake IF EXISTS` followed by `CREATE USER jake SET PASSWORD 'abcd1234'`.
 
-[role=label--new-5.24]
+[role=]
 The equivalent command using the xref:authentication-authorization/auth-providers.adoc[auth providers] syntax would be:
 
 [source,cypher,role=noplay]
@@ -1004,7 +1004,7 @@ Where:
 <1> Specifies the command to alter a user.
 <2> Removes the home database for the user.
 As a result, the DBMS default database will be used as the home database for that user.
-<3> label:new[Introduced in 5.24] Removes one, several, or all existing xref:authentication-authorization/auth-providers.adoc[auth provider(s)] from a user.
+<3> Removes one, several, or all existing xref:authentication-authorization/auth-providers.adoc[auth provider(s)] from a user.
 However, a user must always have at least one auth provider.
 Therefore, `REMOVE ALL AUTH` must be used in conjunction with at least one `SET AUTH` clause in order to meet this requirement.
 <4> Specifies the password for the user.
@@ -1023,7 +1023,7 @@ The `SET PASSWORD` prefix of the `CHANGE [NOT] REQUIRED` clause is only optional
 <6> Specifies the user's status.
 <7> Specifies a home database for a user. A home database is resolved if it is pointing to a database or a database alias. If no home database is set, the DBMS default database is used as the home database for that user.
 
-<8> label:new[Introduced in 5.24] One or more `SET AUTH` clauses can be used to set xref:authentication-authorization/auth-providers.adoc[auth providers], which define authentication / authorization providers for that user.
+<8> One or more `SET AUTH` clauses can be used to set xref:authentication-authorization/auth-providers.adoc[auth providers], which define authentication / authorization providers for that user.
 This might be used to configure external auth providers like LDAP or OIDC, but can also be used as an alternative way to set the native (password-based) auth settings like `SET PASSWORD` and `SET PASSWORD CHANGE REQUIRED`.
 For further informations, see the examples in this section, as well as xref:authentication-authorization/sso-integration.adoc#auth-sso-auth-providers[Configure SSO at the user level using auth providers], and xref:authentication-authorization/ldap-integration.adoc#auth-ldap-auth-providers[Configure authentication/authorization at the user level using auth providers].
 +
@@ -1050,7 +1050,7 @@ SET PASSWORD 'abcd5678' CHANGE NOT REQUIRED
 SET STATUS ACTIVE
 ----
 
-[role=label--new-5.24]
+[role=]
 The equivalent command using the xref:authentication-authorization/auth-providers.adoc[auth providers] syntax would be:
 
 ----
@@ -1070,7 +1070,7 @@ ALTER USER bob
 SET PASSWORD CHANGE REQUIRED
 ----
 
-[role=label--new-5.24]
+[role=]
 The equivalent command using the xref:authentication-authorization/auth-providers.adoc[auth providers] syntax would be:
 
 ----
@@ -1079,7 +1079,7 @@ SET AUTH 'native' {SET PASSWORD CHANGE REQUIRED}
 ----
 ======
 
-[role=label--enterprise-edition label--new-5.24]
+[role=label--enterprise-edition]
 .Modify a user to use an external OIDC auth provider
 ======
 For example, you can modify the user `bob` by removing his native auth provider and adding an external OIDC auth provider:
@@ -1092,7 +1092,7 @@ SET AUTH 'oidc-mysso1' {SET ID 'bobsUniqueMySso1Id'}
 ----
 ======
 
-[role=label--enterprise-edition label--new-5.24]
+[role=label--enterprise-edition]
 .Modify a user to use multiple external OIDC auth providers
 ======
 For example, you can modify the user `bob` by removing all of his existing auth providers and adding two external OIDC auth providers:

modules/ROOT/pages/authentication-authorization/sso-integration.adoc

@@ -271,7 +271,7 @@ dbms.security.oidc.mysso.get_groups_from_user_info=true
 +
 It is possible to fetch just the username, just the groups, or both from the userinfo endpoint.
 
-[role=label--new-5.24]
+[role=]
 [[auth-sso-auth-providers]]
 === Configure SSO at the user level using auth providers
 xref:authentication-authorization/auth-providers.adoc[User auth providers] can be used to determine which users can authenticate and authorize using the configured providers.

modules/ROOT/pages/backup-restore/aggregate.adoc

@@ -90,7 +90,7 @@ Consult Neo4j support before use.
 |false
 
 |--temp-path=<path>
-|label:new[Introduced in 5.24] Provide a path to a temporary empty directory for storing backup files until the command is completed. The files will be deleted once the command is finished.
+|Provide a path to a temporary empty directory for storing backup files until the command is completed. The files will be deleted once the command is finished.
 |
 
 |--verbose
@@ -151,7 +151,7 @@ The following examples show how to perform aggregation of a set of backups locat
 
 [.tabbed-example]
 =====
-[role=include-with-AWS-S3 label--new-5.19]
+[role=include-with-AWS-S3]
 ======
 
 include::partial$/aws-s3-overrides.adoc[]
@@ -167,7 +167,7 @@ bin/neo4j-admin database aggregate-backup --from-path=s3://myBucket/myDirectory/
 ----
 ======
 
-[role=include-with-Google-cloud-storage label--new-5.21]
+[role=include-with-Google-cloud-storage]
 ======
 
 include::partial$/gcs-credentials.adoc[]
@@ -181,7 +181,7 @@ bin/neo4j-admin database aggregate-backup --from-path=gs://myBucket/myDirectory/
 ----
 ======
 
-[role=include-with-Azure-cloud-storage label--new-5.24]
+[role=include-with-Azure-cloud-storage]
 ======
 
 include::partial$/azb-credentials.adoc[]

modules/ROOT/pages/backup-restore/copy-database.adoc

@@ -111,7 +111,7 @@ Cannot be combined with `--ignore-relationships-with-types`.
 |
 
 |--copy-schema
-|label:new[Introduced in 5.20] Copy the schema instead of generating schema statements, meaning index and constraint definitions.
+|Copy the schema instead of generating schema statements, meaning index and constraint definitions.
 The indexes will be built the first time the database is started.
 |
 
@@ -175,7 +175,7 @@ Cannot be combined with `--skip-properties` or `--copy-only-relationship-propert
 |
 
 |--temp-path=<path>
-|label:new[Introduced in 5.24] Path to a directory to be used as a staging area when the source and target databases are the same. Default is the current directory.
+|Path to a directory to be used as a staging area when the source and target databases are the same. Default is the current directory.
 |
 
 |--to-format=<format>
@@ -206,7 +206,7 @@ If you go from `high_limit` to `standard` or `aligned`, there is no validation t
 [role=label--enterprise-edition]
 [NOTE]
 ====
-The block format is introduced in Neo4j 5.14 and from Neo4j 5.22, is the default format for all newly-created databases as long as they do not have the xref:configuration/configuration-settings.adoc#config_db.format[`db.format`] setting specified.
+The block format is the default format for all newly-created databases as long as they do not have the xref:configuration/configuration-settings.adoc#config_db.format[`db.format`] setting specified.
 For more information on the block format, see xref:database-internals/store-formats.adoc[Store formats].
 ====
 
@@ -323,7 +323,7 @@ bin/neo4j-admin database copy neo4j neo4j --compact-node-store --temp-path=<my-p
 +
 [TIP]
 ====
-`--temp-path`, introduced in Neo4j 5.24, can be used to specify a different directory to use as a temporary staging area.
+`--temp-path` can be used to specify a different directory to use as a temporary staging area.
 If omitted, the current working directory will be used.
 
 From Neo4j 5.20 onwards, you can use the `--copy-schema` option to automatically copy the schema.

modules/ROOT/pages/backup-restore/offline-backup.adoc

@@ -130,7 +130,7 @@ The following examples show how to dump a database to a cloud storage bucket usi
 
 [.tabbed-example]
 =====
-[role=include-with-AWS-S3 label--new-5.19]
+[role=include-with-AWS-S3]
 ======
 
 include::partial$/aws-s3-overrides.adoc[]
@@ -145,7 +145,7 @@ bin/neo4j-admin database dump mydatabase --to-path=s3://myBucket/myDirectory/
 ----
 ======
 
-[role=include-with-Google-cloud-storage label--new-5.21]
+[role=include-with-Google-cloud-storage]
 ======
 
 include::partial$/gcs-credentials.adoc[]
@@ -158,7 +158,7 @@ bin/neo4j-admin database dump mydatabase --to-path=gs://myBucket/myDirectory/
 ----
 ======
 
-[role=include-with-Azure-cloud-storage label--new-5.24]
+[role=include-with-Azure-cloud-storage]
 ======
 
 include::partial$/azb-credentials.adoc[]

modules/ROOT/pages/backup-restore/online-backup.adoc

@@ -170,7 +170,7 @@ Note: this is an EXPERIMENTAL option. Consult Neo4j support before use.
 |false
 
 |--temp-path=<path>
-|label:new[Introduced in 5.24] Provide a path to a temporary empty directory for storing backup files until the command is completed. The files will be deleted once the command is finished.
+|Provide a path to a temporary empty directory for storing backup files until the command is completed. The files will be deleted once the command is finished.
 |
 
 |--to-path=<path>
@@ -420,7 +420,7 @@ The following examples show how to back up a database to a cloud storage bucket
 
 [.tabbed-example]
 =====
-[role=include-with-AWS-S3 label--new-5.19]
+[role=include-with-AWS-S3]
 ======
 
 include::partial$/aws-s3-overrides.adoc[]
@@ -436,7 +436,7 @@ bin/neo4j-admin database backup --to-path=s3://myBucket/myDirectory/ mydatabase
 
 ======
 
-[role=include-with-Google-cloud-storage label--new-5.21]
+[role=include-with-Google-cloud-storage]
 ======
 
 include::partial$/gcs-credentials.adoc[]
@@ -448,7 +448,7 @@ include::partial$/gcs-credentials.adoc[]
 bin/neo4j-admin database backup --to-path=gs://myBucket/myDirectory/ mydatabase
 ----
 ======
-[role=include-with-Azure-cloud-storage label--new-5.24]
+[role=include-with-Azure-cloud-storage]
 ======
 
 include::partial$/azb-credentials.adoc[]