Release 0.13.0

Summary

For #349 (closed) Insert a meaningful description for this merge request here: What is the new/changed behavior? Which bug has been fixed? Are there related issues?

Focus

Point the reviewer to the core of the code change. Where should they start reading? What should they focus on (e.g. security, performance, maintainability, user-friendliness, compliance with the specs, finding more corner cases, concrete questions)?

Test Environment

How to set up a test environment for manual testing?

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related issues
• Up-to-date CHANGELOG.md (or not necessary)
• Up-to-date JSON schema (or not necessary)
• Appropriate user and developer documentation (or not necessary)
  • How do I use the software? Assume "stupid" users.
  • How do I develop or debug the software? Assume novice developers.
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md (or not necessary)
• Appropriate user and developer documentation (or not necessary)
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there specifications? Are they satisfied?

For further good practices have a look at our review guidelines.

CHANGELOG.md

@@ -5,6 +5,18 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.13.0] - 2024-10-24
+
+### Changed
+
+* Update LinkAhead MariaDB Backend to [version
+  8.0.0](https://gitlab.com/linkahead/linkahead-mariadbbackend/-/releases/v8.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)
+  in the LinkAhead MariaDB Backend repo for more information and a
+  script to update incompatible dumps.
+
 ## [0.12.3] - 2024-09-25
 
 ### Fixed
@@ -83,14 +95,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)
@@ -296,12 +308,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