DOC: Update changleog

CHANGELOG.md

@@ -11,6 +11,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Changed
 
+* Update LinkAhead MariaDB Backend to version 8.0.0 to make LinkAhead
+  compatible to MariaDB >= 10.6. Old SQL dumps may be incompatible to
+  MariaDB 10.6 and above; see
+  [`update_dumps/README.md`](https://gitlab.com/linkahead/linkahead-mariadbbackend/-/blob/main/dump_updates/README.md?ref_type=heads)
+  for more information and a script to update incompatible dumps.
+
 ### Deprecated
 
 ### Removed
@@ -97,14 +103,14 @@ sensitive information. See the bug reports for more information.
 * The default behavior of the query `FIND SomeName [...]` (as well as COUNT and SELECT) is being
   made configurable and changes:
   * `FIND SomeName` will be interpreted as `FIND <FIND_QUERY_DEFAULT_ROLE>
-    SomeName` from now on where `FIND_QUERY_DEFAULT_ROLE` is a newly introduced
-    server property.
+	SomeName` from now on where `FIND_QUERY_DEFAULT_ROLE` is a newly introduced
+	server property.
   * The new `FIND_QUERY_DEFAULT_ROLE` server property defaults to `RECORD`
-    which is why the behavior of the server api has a **breaking change**.
+	which is why the behavior of the server api has a **breaking change**.
   * The semantics of `FIND *` are affected as well. `FIND *` is equivalent to
-    `FIND <FIND_QUERY_DEFAULT_ROLE>`.
+	`FIND <FIND_QUERY_DEFAULT_ROLE>`.
   * Of course, administrators can choose to retain the old behavior by setting
-    `FIND_QUERY_DEFAULT_ROLE=ENTITY`.
+	`FIND_QUERY_DEFAULT_ROLE=ENTITY`.
 * CQL now treats `WITH` and `WITH A` equivalently. Issue: [#192](https://gitlab.com/caosdb/caosdb-server/-/issues/192)
 * The InsertFilesInDir FlagJob now creates File entities without a name.  The previous behavior
   caused severe performance problems for very large numbers of files. Issue: [#197](https://gitlab.com/caosdb/caosdb-server/-/issues/197)
@@ -310,12 +316,12 @@ process. It is identical to v0.7.1
   "authentication" header.
   Notable limitations of the current implementation of the API:
   * It is currently not possible to mix retrievals
-    (caosdb.entity.v1.RetrieveRequest) with any other transaction type - so
-    transaction are either read-only or write-only. The server throws an error
-    if it finds mixed read/write transactions.
+	(caosdb.entity.v1.RetrieveRequest) with any other transaction type - so
+	transaction are either read-only or write-only. The server throws an error
+	if it finds mixed read/write transactions.
   * It is currently not possible to have more that one query
-    (caosdb.entity.v1.Query) in a single transaction. The server throws an
-    error if it finds more than one query.
+	(caosdb.entity.v1.Query) in a single transaction. The server throws an
+	error if it finds more than one query.
 
 
 ### Changed