changelog-2.adoc-include

////
Note: this file (changelog-2.adoc-include) is generated automatically.
Do not make manual changes in this file, as they will be lost.

If you want to add changelog entries, create a new file in changelog/src/changelog/entries/... and run creation of the changelog with
mvn -pl changelog install
////

[[v3.2.12]]
== 3.2.12 (13.07.2026)

[[v3.2.11]]
== 3.2.11 (03.07.2026)

icon:check[] Schema Migrations, which renamed multiple fields and additionally created new fields using the old names but different field types always failed.
This has been fixed.


[[v3.2.10]]
== 3.2.10 (12.06.2026)

[[v3.2.9]]
== 3.2.9 (12.05.2026)

[[v3.2.8]]
== 3.2.8 (24.04.2026)

[[v3.2.7]]
== 3.2.7 (21.04.2026)

[[v3.2.6]]
== 3.2.6 (13.04.2026)

[[v3.2.5]]
== 3.2.5 (17.03.2026)

[[v3.2.4]]
== 3.2.4 (25.02.2026)

[[v3.2.3]]
== 3.2.3 (11.02.2026)

[[v3.2.2]]
== 3.2.2 (06.02.2026)

[[v3.2.1]]
== 3.2.1 (12.01.2026)

[[v3.2.0]]
== 3.2.0 (16.12.2025)

icon:plus[] Search: An index search integration with Elasticsearch has been refactored to use the stateless `search_after` approach. The old, `scroll` API based implementation has been removed.

icon:plus[] Search: Support for Elasticsearch 9 has been added.

icon:plus[] Core: The `Vert.x` async IO / routing framework has been updated to the version `5.0.5`.

icon:plus[] Some dependencies have been updated:
* Hibernate: 7.1.8.Final


[[v3.1.18]]
== 3.1.18 (13.07.2026)

icon:check[] Core: An extra check on the nodes, eligible for the migration, is performed to avoid early finish of the migration process, caused by inconsistent node data.

icon:check[] Core: An inconsistency case of a content edge pointing to the missing content record now has a repair mechanism.

icon:check[] Schema Migrations, which renamed multiple fields and additionally created new fields using the old names but different field types always failed.
This has been fixed.


icon:check[] Core: The performance of updating (micro)schemas has been improved. 

icon:check[] Core: An edge case, causing micronode list update to keep the failing thread running, with a possibility to DDoS, has been eliminated.

icon:check[] Elasticsearch: Fixed a possible NullPointerException when the search.mappingMode was set to STRICT and
no custom mapping was configured for at least one field in a schema.


[[v3.1.17]]
== 3.1.17 (12.06.2026)

icon:check[] Core: A crash on requesting node children recursively through GraphQL + native filtering has been fixed.

[[v3.1.16]]
== 3.1.16 (12.05.2026)

icon:check[] Core: An edge case of constructing a database request with too many parameters has been fixed.

icon:check[] Core: When enabling the hibernate second level caches, the used cache instance were configured without limits, which
effectively could lead to OOM errors.
New configuration settings have been introduced to configure the limits for those caches in clustered and non-clustered instances:
* `cache.clusteredHibernateCacheHeapFree` defines the required amount of free heap space in clustered instances (defaults to `10%`)
* `cache.nonClusteredHibernateCacheSize` defines the maximum cache size in non-clustered instances (defaults to `50_000`)


icon:check[] Core: When the initialization of an instance failed (e.g. due to unavailability of the database),
the process could fail to terminate. This has been fixed.


[[v3.1.15]]
== 3.1.15 (24.04.2026)

icon:check[] Core: A crash during fetching micronode data, referenced through multiple lists, has been fixed.

[[v3.1.14]]
== 3.1.14 (21.04.2026)

[[v3.1.13]]
== 3.1.13 (13.04.2026)

[[v3.1.12]]
== 3.1.12 (17.03.2026)

icon:check[] Fixed classpath static handler to return 404 for directory requests instead of caching them as files in plugin storage

icon:check[] GraphQL: The performance of loading nodes with filters has been improved by reducing the number
of required SQL queries.


icon:check[] Core: Additional indices have been added to improve query performance. The indices will be created during startup
of Mesh, which might increase the first startup time after updating to this version.


icon:check[] Rest Client: Validation of parameters has been improved.


[[v3.1.11]]
== 3.1.11 (25.02.2026)

icon:check[] Elasticsearch: When an ES server is unresponsive, a timeout error is thrown, which may or may not have a HTTP body. In the case of body absence Mesh crashes with HTTP 500. This has now been fixed.

icon:check[] Monitoring: Mesh will now regularly monitor memory consumption and garbage collections.
See "Monitoring":https://www.gentics.com/mesh/docs/monitoring/ in the documentation for details.


icon:check[] REST API: Handling of schema or microschema updates has been improved to not create new versions if nothing was actually changed.


icon:check[] REST API: Performance of getting schemas/microschemas assigned to a branch has been improved
if schemas/microschemas exist, that have lots of versions.


icon:check[] Core: A consistency check and repair for incorrectly linked content versions has been added.


[[v3.1.10]]
== 3.1.10 (11.02.2026)

icon:check[] Core: A number of exceptions regarding inexisting message translations has been eliminated.

icon:check[] GraphQL: Loading of a node field which references a deleted node resulted in an error message in the response.
This has been fixed.


[[v3.1.9]]
== 3.1.9 (06.02.2026)

icon:check[] GraphQL: The number of SQL Queries necessary for fetching breadcrumbs and node references via GraphQL has been reduced.


icon:check[] REST API: Requests to create or update nodes with fields exceeding the length limit will now fail with an appropriate error message.


icon:check[] The version of the library for handling GraphQL filtering has been updated to
remove the unnecessary dependency on AssertJ.


[[v3.1.8]]
== 3.1.8 (12.01.2026)

icon:check[] Core: A permission system has been reworked to speed up accessibility of the selected elements for the users with admin permissions. 

[[v3.1.7]]
== 3.1.7 (12.12.2025)

icon:check[] Docker: The content of @eclipse-temurin@ base image has been updated, to eliminate critical vulnerabilities on its dependencies.

[[v3.1.6]]
== 3.1.6 (20.11.2025)

icon:check[] Core: The published status of the fetched content was wrong, if using either native filtering or sorting. This has been fixed.

icon:check[] Core: The API for branches has been modified to support better performance when loading
the latest schema version of a schema in a branch.


icon:check[] Core: The performace for creating/updating nodes has been improved.


icon:check[] Core: The second level cache for hibernate has been enabled by default.
The startup of Mesh with second level cache enabled in a cluster environment has been fixed.


icon:check[] Core: The performance of getting entity lists has been improved by reducing the number of executed SQL queries.


icon:check[] Core: The `OkHttp` client dependency has been updated to the version `5.3.0`, targeting the vulnerability `CVE-2021-0341`. 
The `ElasticSearch Java Client`, that depends on the same client, has been updated as well to the version `1.1.4`.

[[v3.1.5]]
== 3.1.5 (27.10.2025)

icon:check[] Core: After the data migration from the older Mesh versions it is possible to have list item database tables being polluted with the duplicated data, that, while making no functional harm, may lead to the random performance penalties.
 Targeting these, a new consistency check/repair feature has been added to the existing "*listitem" checks. 

icon:check[] Search: Running an index sync did not properly close all used scroll contexts in elasticsearch,
which could lead to errors like 'Trying to create too many scroll contexts' in elasticsearch.
This has been fixed, all scroll contexts are closed as soon as they are not used any more.


icon:check[] Core: Under some circumstances the fetch of entities via REST GET returns duplicated entries. This has been fixed.

icon:check[] Core: The recursive deletion of nodes has been fixed to not leave orphaned contents behind.


[[v3.1.4]]
== 3.1.4 (23.09.2025)

icon:check[] Core: Generation of ETags for nodes has generally been improved to be more stable.


icon:check[] Core: Generation of childrenInfo and etag for nodes with many children has been refactored to support better performance.


icon:check[] Core: Generation of childrenInfo and etag for nodes with many children has been made more performant.


icon:check[] GraphQL: The performance of GraphQL queries returning larger hierachies of data has been improved.


icon:check[] Core: The performance of deleting nodes recursively has been improved.


icon:check[] Core: Implementations of the persistance layer may now choose to process recursive deletion of nodes
in a separate thread instead of in the worker thread pool.


icon:check[] Core: Deleting of nodes with more than 1000 descendants is now done
in a separate thread. This will also cause those delete tasks to be done
one after the other instead of in parallel.


icon:check[] Search: When a schema was completely excluded from indexing, the index sync operation still
tried to put the nodes of that schema into the non-existent index, this has been fixed.


icon:check[] Core: It is now possible to delete a node with a list field that has data inconsistencies.

[[v3.1.3]]
== 3.1.3 (01.09.2025)

icon:check[] Plugins: Now the plugin timeout value is also considered in the HTTP plugin client. This allows extending HTTP call timeouts when the plugin is expected to start longer.

icon:check[] Some dependencies have been updated:
* Netty: 4.1.124.Final
* Vert.x: 4.5.18


icon:check[] Core: The following dependencies have been updated, to target the vulnerability CVE-2025-54988 :
 * Apache Tika, to *3.2.2*
 * Apache Commons Lang3, to *3.18.0*
 * Apache Commons Compress, to *1.28.0*
 * JSOUP, to *1.21.1*

[[v3.1.2]]
== 3.1.2 (15.07.2025)

icon:check[] Core: Generation of ETags for nodes containing tags was not stable and sometimes resulted in different ETags,
even if nothing was changed. This has been fixed.


icon:check[] REST API: Now Mesh accepts both ISO-8601 standards of a date/time string representation, with and without trailing Z or timezone value.

[[v3.1.1]]
== 3.1.1 (03.07.2025)

icon:plus[] Core: The following dependencies have been updated, to eliminate vulnerable versions:
 * Vert.x - to version `4.5.14`
 * Netty - to version `4.1.118.Final`

icon:check[] REST: The query parameters for node versioning and branch targeting have been decoupled, to match the cases where a branch usage is allowed, but version is not.

Documentation: The query parameterizing has been updated for the selected REST endpoints.

icon:check[] Auth: Now a secondary auth provider (from Mesh plugins, for instance) allows proceeding with the request unauthenticated in a number of cases of errors, like provider denial or bad request, and logging the other cases.

[[v3.1.0]]
== 3.1.0 (10.06.2025)

icon:plus[] Some dependencies have been updated:
* Hibernate: 6.6.11.Final
* Vert.x: 4.5.14
* Netty: 4.1.118.Final
* Spring Security: 6.3.5
* Guava: 32.0.0-jre
* Zip4j: 2.11.3
* Logback: 1.5.18
* Okio: 1.17.6
* Dagger: 2.56.2


icon:check[] Some dependencies have been updated:
* Netty: 4.1.118.Final
* Commons Beanutils: 1.11.0


[[v3.0.17]]
== 3.0.17 (20.11.2025)

icon:check[] Core: The published status of the fetched content was wrong, if using either native filtering or sorting. This has been fixed.

icon:check[] Core: The API for branches has been modified to support better performance when loading
the latest schema version of a schema in a branch.


icon:check[] Core: The performace for creating/updating nodes has been improved.


icon:check[] Core: The second level cache for hibernate has been enabled by default.
The startup of Mesh with second level cache enabled in a cluster environment has been fixed.


icon:check[] Core: The performance of getting entity lists has been improved by reducing the number of executed SQL queries.


icon:check[] Core: The `OkHttp` client dependency has been updated to the version `5.3.0`, targeting the vulnerability `CVE-2021-0341`. 
The `ElasticSearch Java Client`, that depends on the same client, has been updated as well to the version `1.1.4`.

[[v3.0.16]]
== 3.0.16 (27.10.2025)

icon:check[] Core: After the data migration from the older Mesh versions it is possible to have list item database tables being polluted with the duplicated data, that, while making no functional harm, may lead to the random performance penalties.
 Targeting these, a new consistency check/repair feature has been added to the existing "*listitem" checks. 

icon:check[] Search: Running an index sync did not properly close all used scroll contexts in elasticsearch,
which could lead to errors like 'Trying to create too many scroll contexts' in elasticsearch.
This has been fixed, all scroll contexts are closed as soon as they are not used any more.


icon:check[] Core: Under some circumstances the fetch of entities via REST GET returns duplicated entries. This has been fixed.

icon:check[] Core: The recursive deletion of nodes has been fixed to not leave orphaned contents behind.


[[v3.0.15]]
== 3.0.15 (23.09.2025)

icon:check[] Core: Generation of ETags for nodes has generally been improved to be more stable.


icon:check[] Core: Generation of childrenInfo and etag for nodes with many children has been refactored to support better performance.


icon:check[] Core: Generation of childrenInfo and etag for nodes with many children has been made more performant.


icon:check[] GraphQL: The performance of GraphQL queries returning larger hierachies of data has been improved.


icon:check[] Core: The performance of deleting nodes recursively has been improved.


icon:check[] Core: Implementations of the persistance layer may now choose to process recursive deletion of nodes
in a separate thread instead of in the worker thread pool.


icon:check[] Core: Deleting of nodes with more than 1000 descendants is now done
in a separate thread. This will also cause those delete tasks to be done
one after the other instead of in parallel.


icon:check[] Search: When a schema was completely excluded from indexing, the index sync operation still
tried to put the nodes of that schema into the non-existent index, this has been fixed.


icon:check[] Core: It is now possible to delete a node with a list field that has data inconsistencies.

[[v3.0.14]]
== 3.0.14 (01.09.2025)

icon:check[] Plugins: Now the plugin timeout value is also considered in the HTTP plugin client. This allows extending HTTP call timeouts when the plugin is expected to start longer.

icon:check[] Some dependencies have been updated:
* Netty: 4.1.124.Final
* Vert.x: 4.5.18


icon:check[] Core: The following dependencies have been updated, to target the vulnerability CVE-2025-54988 :
 * Apache Tika, to *3.2.2*
 * Apache Commons Lang3, to *3.18.0*
 * Apache Commons Compress, to *1.28.0*
 * JSOUP, to *1.21.1*

[[v3.0.13]]
== 3.0.13 (15.07.2025)

icon:check[] Core: Generation of ETags for nodes containing tags was not stable and sometimes resulted in different ETags,
even if nothing was changed. This has been fixed.


icon:check[] REST API: Now Mesh accepts both ISO-8601 standards of a date/time string representation, with and without trailing Z or timezone value.

[[v3.0.12]]
== 3.0.12 (02.07.2025)

icon:check[] REST: The query parameters for node versioning and branch targeting have been decoupled, to match the cases where a branch usage is allowed, but version is not.

Documentation: The query parameterizing has been updated for the selected REST endpoints.

icon:check[] Auth: Now a secondary auth provider (from Mesh plugins, for instance) allows proceeding with the request unauthenticated in a number of cases of errors, like provider denial or bad request, and logging the other cases.

[[v3.0.11]]
== 3.0.11 (20.06.2025)

icon:plus[] Core: The following dependencies have been updated, to eliminate vulnerable versions:
 * Vert.x - to version `4.5.14`
 * Netty - to version `4.1.118.Final`

icon:check[] Some dependencies have been updated:
* Netty: 4.1.118.Final
* Commons Beanutils: 1.11.0


[[v3.0.10]]
== 3.0.10 (22.05.2025)

icon:check[] Plugins: If a static file handler fails to unpack the static resource to the plugin storage folder, currently a misleading `HTTP 404 binary_data_not_found` is thrown. This has been now changed to `HTTP 500` with a detailed failure description.

[[v3.0.9]]
== 3.0.9 (07.05.2025)

icon:check[] Auth: More occurrences of setting the `mesh.token` cookies have been secured with `HTTPOnly` flag.

icon:check[] Image Manipulation: Creating image variants with a focal point or focal zoom value failed with an internal server error when using MariaDB.
This has been fixed.


[[v3.0.8]]
== 3.0.8 (24.04.2025)

icon:check[] S3: Now the language specific S3 fields are correctly processed.

[[v3.0.7]]
== 3.0.7 (10.04.2025)

icon:check[] The dependency on nashorn-core has been updated to 15.6.
This fixes startup errors in plugins (like the comment plugin) which uses precompilation of handlebars templates to javascript.


icon:check[] Logging: Some sensitive configuration entries were eliminated from the logging.

icon:check[] S3: When a S3 image is transformed, the transformation result can be never returned to the client at some cases, because of a false cache path provided by the transformation service. This has been fixed.

icon:check[] Core: When an empty payload is sent to the binary field update function, a new version of a content, being updated, is produced, containing no changes. This has been now fixed, and the content stays old in this case. 

icon:check[] OAuth: If a new set of groups/roles has been attached to the Mesh user during the OAuth login session, these groups/roles are not used in the filtering during the same session. This has been fixed. 

icon:check[] Indexing: At some circumstances an indexing engine crash is possible, when the changes, triggering the (re)indexing on updated or deleted data, come too quickly. This has been fixed.

icon:check[] The dependencies on hibernate have been changed from groupId org.hibernate to org.hibernate.orm.


[[v3.0.6]]
== 3.0.6 (26.03.2025)

[[v3.0.5]]
== 3.0.5 (13.03.2025)

icon:plus[] Documentation: References to the MariaDB official documentation have been added.

[[v3.0.4]]
== 3.0.4 (26.02.2025)

icon:check[] Auth: The JWT auth cookie will now have the `HTTPOnly` flag set.


[[v3.0.3]]
== 3.0.3 (12.02.2025)

icon:check[] Image Manipulation: A periodic cleanup for files in the image cache has been added, which can be
configured with the new configuration options `image.imageCacheCleanInterval` (for the interval for running the cleanup)
and `image.imageCacheMaxIdle` (for the maximum allowed file age). Both values must be set in ISO 8601 duration format.
By default, `image.imageCacheCleanInterval` is set to `PT0S` (0 seconds), which deactivates the periodic cleanup.


icon:check[] GraphQL: A case of using a GraphQL native filter for a string field against a UUID value, resulting in an exception, has been fixed. 

[[v3.0.2]]
== 3.0.2 (29.01.2025)

icon:check[] Core: The processing of binaries has been refactored, targeting possible binary data leftovers being eliminated after the binary content is updated or deleted. Also, two new async consistency check have been added, for the detection of binary data with no corresponding database records (repairable) and binary database records with no corresponding binary data (for the automated testing purposes, not repairable).

[[v3.0.1]]
== 3.0.1 (16.01.2025)

icon:check[] GraphQL: Data fetchers have been speed up on native filtering of the nodes with node fields, by fixing the proper context detection, so complex multi-inclusion queries (navigation) run up to 10x faster.


icon:check[] Core: The node deletion rules has been strictened, to avoid internal deletion API misusage.

icon:check[] Auth: A crash on retrieving principal user's referenced node has been fixed.

icon:check[] Cache: The Image Cache refactoring, which was done in a previous hotfix release introduced an error which caused creation of empty folders in the old structure as well. This has been fixed.
Also the migration process has been fixed to really remove all folders of the old structure, even if they are empty or contain cache files of binaries that were deleted before.


icon:check[] Clustering: Autodiscovery of cluster member nodes in a kubernetes environment did not work (Mesh instances failed to start) due to an incorrect dependency, which has been removed now.


icon:check[] GraphQL: A natively filtered paginated data set contains incorrect values for current page and total page number. This has been fixed.

icon:check[] Core: The paged data sets contain different data, when being produced by native and legacy filtering, and/or sorting, under some circumstances. This has been fixed.

[[v3.0.0]]
== 3.0.0 (09.12.2024)

icon:bullhorn[] Core: The storage layer has been replaced from the included OrientDB to the Hibernate ORM based solution, allowing the usage of 3rd party SQL RDBMS as a structured data storage. The supported database for Mesh OSS is MariaDB 10.7+.  Additionally, an in-memory mode HSQLDB is supported for the testing purposes.

icon:plus[] Search: Adds compliance mode ES_8 for Elasticsearch 8.x.

icon:plus[] SQL: The Liquibase library, responsible for the fluent update of the low level relational database structure, has been updated to the version @4.29.2@.

icon:plus[] Core: An Apache Tika file parsing dependency has been updated to the version `2.9.2`.

icon:plus[] Clustering: The Hazelcast library, responsible for the cluster instances orchestration, has been updated to the version @5.5.0@.

icon:plus[] Some library dependencies have been updated to the latest hotfix versions.


[[v2.1.25]]
== 2.1.25 (27.10.2025)

icon:check[] Search: Running an index sync did not properly close all used scroll contexts in elasticsearch,
which could lead to errors like 'Trying to create too many scroll contexts' in elasticsearch.
This has been fixed, all scroll contexts are closed as soon as they are not used any more.


[[v2.1.24]]
== 2.1.24 (22.09.2025)

icon:check[] Core: Generation of ETags for nodes has generally been improved to be more stable.


icon:check[] Core: Generation of childrenInfo and etag for nodes with many children has been refactored to support better performance.


icon:check[] GraphQL: The performance of GraphQL queries returning larger hierachies of data has been improved.


icon:check[] Core: Implementations of the persistance layer may now choose to process recursive deletion of nodes
in a separate thread instead of in the worker thread pool.


icon:check[] Search: When a schema was completely excluded from indexing, the index sync operation still
tried to put the nodes of that schema into the non-existent index, this has been fixed.


[[v2.1.23]]
== 2.1.23 (01.09.2025)

icon:check[] Core: Generation of ETags for nodes containing tags was not stable and sometimes resulted in different ETags,
even if nothing was changed. This has been fixed.


icon:check[] Plugins: Now the plugin timeout value is also considered in the HTTP plugin client. This allows extending HTTP call timeouts when the plugin is expected to start longer.

[[v2.1.22]]
== 2.1.22 (02.07.2025)

icon:check[] REST: The query parameters for node versioning and branch targeting have been decoupled, to match the cases where a branch usage is allowed, but version is not.

Documentation: The query parameterizing has been updated for the selected REST endpoints.

icon:check[] Auth: Now a secondary auth provider (from Mesh plugins, for instance) allows proceeding with the request unauthenticated in a number of cases of errors, like provider denial or bad request, and logging the other cases.

[[v2.1.21]]
== 2.1.21 (20.06.2025)

icon:plus[] Core: The following dependencies have been updated, to eliminate vulnerable versions:
 * Vert.x - to version `4.5.14`
 * Netty - to version `4.1.118.Final`

[[v2.1.20]]
== 2.1.20 (22.05.2025)

icon:check[] Plugins: If a static file handler fails to unpack the static resource to the plugin storage folder, currently a misleading `HTTP 404 binary_data_not_found` is thrown. This has been now changed to `HTTP 500` with a detailed failure description.

[[v2.1.19]]
== 2.1.19 (07.05.2025)

icon:check[] Auth: More occurrences of setting the `mesh.token` cookies have been secured with `HTTPOnly` flag.

[[v2.1.18]]
== 2.1.18 (23.04.2025)

icon:check[] S3: Now the language specific S3 fields are correctly processed.

[[v2.1.17]]
== 2.1.17 (25.03.2025)

icon:check[] S3: When a S3 image is transformed, the transformation result can be never returned to the client at some cases, because of a false cache path provided by the transformation service. This has been fixed.

icon:check[] Core: When an empty payload is sent to the binary field update function, a new version of a content, being updated, is produced, containing no changes. This has been now fixed, and the content stays old in this case. 

icon:check[] OAuth: If a new set of groups/roles has been attached to the Mesh user during the OAuth login session, these groups/roles are not used in the filtering during the same session. This has been fixed. 

icon:check[] Indexing: At some circumstances an indexing engine crash is possible, when the changes, triggering the (re)indexing on updated or deleted data, come too quickly. This has been fixed.

[[v2.1.16]]
== 2.1.16 (12.03.2025)

icon:check[] The dependency on nashorn-core has been updated to 15.6.
This fixes startup errors in plugins (like the comment plugin) which uses precompilation of handlebars templates to javascript.


icon:check[] Logging: Some sensitive configuration entries were eliminated from the logging.

[[v2.1.15]]
== 2.1.15 (25.02.2025)

icon:check[] Auth: The JWT auth cookie will now have the `HTTPOnly` flag set.


[[v2.1.14]]
== 2.1.14 (11.02.2025)

icon:check[] Image Manipulation: A periodic cleanup for files in the image cache has been added, which can be
configured with the new configuration options `image.imageCacheCleanInterval` (for the interval for running the cleanup)
and `image.imageCacheMaxIdle` (for the maximum allowed file age). Both values must be set in ISO 8601 duration format.
By default, `image.imageCacheCleanInterval` is set to `PT0S` (0 seconds), which deactivates the periodic cleanup.


[[v2.1.13]]
== 2.1.13 (28.01.2025)

icon:check[] Core: The processing of binaries has been refactored, targeting possible binary data leftovers being eliminated after the binary content is updated or deleted. Also, two new async consistency check have been added, for the detection of binary data with no corresponding database records (repairable) and binary database records with no corresponding binary data (for the automated testing purposes, not repairable).

[[v2.1.12]]
== 2.1.12 (16.01.2025)

icon:check[] Cache: The Image Cache refactoring, which was done in a previous hotfix release introduced an error which caused creation of empty folders in the old structure as well. This has been fixed.
Also the migration process has been fixed to really remove all folders of the old structure, even if they are empty or contain cache files of binaries that were deleted before.


icon:check[] GraphQL: A natively filtered paginated data set contains incorrect values for current page and total page number. This has been fixed.

[[v2.1.11]]
== 2.1.11 (09.12.2024)

icon:check[] GraphQL: Data fetchers have been speed up on native filtering of the nodes with node fields, by fixing the proper context detection, so complex multi-inclusion queries (navigation) run up to 10x faster.


icon:check[] Core: The node deletion rules has been strictened, to avoid internal deletion API misusage.

icon:check[] Auth: A crash on retrieving principal user's referenced node has been fixed.

[[v2.1.10]]
== 2.1.10 (06.11.2024)

icon:plus[] Core: Now it is possible to sort over binary metadata, node reference and micronode non-list fields.

[[v2.1.9]]
== 2.1.9 (23.10.2024)

icon:check[] Documentation: A missing query parameters documentation for the `/search` and `/{{project}}/search` has been added.

icon:check[] Cache: Image cache has been refactored, utilizing now simpler structure with less folder depth.

icon:check[] Core: A potential data loss on an edge case of node migration over several schema versions, including field name/type change, has been fixed.

[[v2.1.8]]
== 2.1.8 (09.10.2024)

icon:check[] Image Manipulation: The validation of resize width and height have been fixed to also properly handle values set to "auto" in the request.

icon:check[] GraphQL: The library for handling GraphQL Filters in Java has been updated to fix inconsistent behaviour when filtering nodes with fields of type "date" or "number",
which had the field set to null.
Before the fix, such nodes were never returned regardless of the used filter. Now the behaviour is identical to filters on fields of other types (such as "string" or "boolean") so that
null values will not natch when compared to non-null values, but the negation with "not" will match.


[[v2.1.7]]
== 2.1.7 (01.10.2024)

icon:check[] Core: A crash, caused by duplicated nodes in a GraphQL resulting set, has been fixed.

[[v2.1.6]]
== 2.1.6 (13.09.2024)

icon:check[] Core: The Vert.x Handlebars engine dependency has been patched, to replace the vulnerable Apache `commons-text` dependency, targeting `CVE-2022-42889`.

[[v2.1.5]]
== 2.1.5 (28.08.2024)

icon:check[] Core: A crash has been fixed on an attempt of (micro)node migration over non-adjacent (micro)schema versions.

[[v2.1.4]]
== 2.1.4 (07.08.2024)

icon:check[] Documentation: The check/repair API calls are better documented in regards of an async processing. The logging documentation is extended with format examples.

[[v2.1.3]]
== 2.1.3 (26.06.2024)

icon:check[] Elasticsearch: An Elasticsearch Java Client has been updated to the version `1.1.2`, containing the corrections to the connection failure processing mechanism. The Elasticsearch activity idle checking has been improved to be more proof of the unstable connections.

[[v2.1.2]]
== 2.1.2 (14.05.2024)

icon:check[] GraphQL: A combination of similar queries with different names and filter parameters, running over native filtering, that produces incorrect results, has been fixed. 

[[v2.1.1]]
== 2.1.1 (02.05.2024)

icon:check[] The library used to process webp images has been changed due to JVM errors when running in an `alpine` based image.


[[v2.1.0]]
== 2.1.0 (26.04.2024)

icon:plus[] Core: Usage of application level protocol negotiation (aka ALPN) can be now configured via Mesh Options.


icon:plus[] Java Rest client: REST client can now choose the HTTP protocol version to use for the Mesh connection. Possible values: DEFAULT (current default support of the carrier HTTP client library, default value), HTTP_1_1, HTTP_2.


icon:plus[] Plugins: An option for connection over HTTP/2 for the Mesh plugins have been added.


icon:plus[] Image manipulation: Adds support for WebP images.

icon:plus[] The endpoint `GET /auth/login` now also supports login via the Authentication Bearer request header (using an API token).


icon:plus[] Core: The on-demand image manipulation feature has been refactored for DDoS protection. The new image manipulator option, `mode`, has been added with the following values: 
`ON_DEMAND` keeps already existing behaviour with creating/reusing the image variant automatically on each request, 
`MANUAL` requires an extra step of calling the image variant creation REST API prior to the variant serve, `OFF` disables the feature completely. A set of REST API calls has been added for the image variants manipulation. 
The GraphQL `nodes` call has been extended to filter/serve over the image variants of a selected binary field, if applicable.

icon:plus[] Search: Several enhancements have been applied to the content, sent to the search engine for the indexing. Each (micro)schema is presented a `noIndex` flag, marking the content of the (micro)schema as excluded from the indexing. Each (micro)schema field is presented a similar `noIndex` flag. 
By default no flag is set, meaning the content to be indexable. This feature serves security purposes, preventing the sensible information from leaking through the search engine. 

icon:plus[] REST: A new HttpServer option, `minifyJson`, has been added to control over the REST API payloads being pretty printed for readability, or minified for resource save. An analogous setting has been added to the Java `MeshRestClient`. 
Default value is `true`, so the payload minification is turned on, which is a @breaking@S change, if one expects the pretty-formatted output.

icon:plus[] Now it's possible to use generated Mesh API key for the login request, with `apikey` string body parameter.

icon:plus[] REST: A new 'languages' endpoint has been added, providing the list of the installed languages, as well as the lookup over UUID or 2-character language tag.

icon:plus[] Some dependencies have been updated:
* VertX: 4.5.7
* GraphQL: 21.5
* GraphQL Dataloader: 3.2.2
* PF4j: 3.11.0
* Hazelcast: 3.12.13
* Jackson: 2.17.0
* SnakeYAML: 2.2
* Log4j: 2.23.1
* SLF4j: 2.0.13
* Logback: 1.5.5
* Commons IO: 2.16.1
* RAML Parser: 0.8.40
* JSON Path: 2.9.0
* JSoup: 1.17.2
* Jettison: 1.5.4
* Netty: 4.1.108.Final
* Image IO: 3.10.1


[[v2.0.20]]
== 2.0.20 (17.04.2024)

[[v2.0.19]]
== 2.0.19 (20.03.2024)

icon:check[] GraphQL: A regression of missing common `and`, `or`, `not` top level filters has been fixed.

[[v2.0.18]]
== 2.0.18 (06.03.2024)

icon:check[] REST client: The configuration now allows adding default parameter provider for query parameters, that should be added to every request (unless overwritten).

Tests: The tests API has been extended to allow tests which do not reset the database between test cases.

[[v2.0.17]]
== 2.0.17 (28.02.2024)

icon:check[] GraphQL: In cases of long running GraphQL requests, some other GraphQL requests were queued and executed after the long running request, even if enough workers were still
available. The behaviour has been changed, so that GraphQL requests will only be queued, if all workers are currently busy.

icon:check[] Cache: The permission cache has been fixed to always return copies of the actually cached entries.

[[v2.0.16]]
== 2.0.16 (22.02.2024)

icon:check[] REST: When requesting sorted data, the permission limitations are violated. This has been fixed.

icon:check[] Core: Creating a translation for the root node of a project always failed with a "Bad Request" error, which has been fixed.

icon:check[] Elasticsearch: A full access to the data backed by ES has been given to the admin users.

icon:check[] Because of a flawed cache invalidation strategy, the project stayed on an old 'latest' branch, even if a new one has been assigned, until the caches are invalidated, or a restart is triggered. This has been fixed.

icon:check[] Cache: A mechanism of reattaching the cached entity to the persistence context has been introduced, allowing implementations of smarter cache policies.

Cache: Because of a flawed cache invalidation strategy, the project stayed on an old 'latest' branch, even if a new one has been assigned, until the caches are invalidated, or a restart is triggered. This has been fixed.

icon:check[] A regression regarding OAuth user filtering has been fixed.

Minor improvements in authentication-related utilities Java API, allowing more control over authentication URL management.

[[v2.0.15]]
== 2.0.15 (08.02.2024)

icon:check[] REST client: Improves error handling for WebSocket errors.

icon:check[] REST: The endpoints for invoking a consistency check/repair now have a new query parameter `async` which allows to perform the action as a background job instead of synchronously.
Core: Updating and publishing a node in a single request has been optimized to only create a single new version of the content.

icon:check[] Auth: Synchronization of users, groups and roles from AuthServicePlugin implementations (like the keycloak plugin) has been improved for performance and stability.

icon:check[] Elasticsearch: A possibility of DDoSing the ES with a bulk request of too many items has been eliminated.

icon:check[] GraphQL: When an inexisting language has been requested for a node, the schema info was not loaded as well. This has been fixed.

[[v2.0.14]]
== 2.0.14 (24.01.2024)

icon:check[] GraphQL: Fetching of micronode fields has been improved to allow batch loading.

[[v2.0.13]]
== 2.0.13 (10.01.2024)

icon:check[] REST: The documentation of the generic parameter `fields` has been fixed. Now `fields` works over the Language entities as well, the values are `uuid`,`name`,`languageTag`,`nativeName`.

icon:check[] GraphQL. Some of (micro)schema fields related queries rely on the target (micro)schema having at least one field, crashing in HTTP 500 otherwise. This has now been fixed. 

[[v2.0.12]]
== 2.0.12 (20.12.2023)

icon:check[] GraphQL: More test cases for sorting have been added.


icon:check[] Core: Unnecessary uniqueness checks for segment fields will now be avoided, when updating nodes.

icon:check[] GraphQL: The overall performance of GraphQL requests has been improved by caching the GraphQL schemas.

icon:check[] Core: Now it is not allowed to set a new password to an empty or invalid (e.g. spaces) string.

icon:check[] Auth: The unnecessary logging of outdated/mismatched auth token has been removed.

[[v2.0.11]]
== 2.0.11 (06.12.2023)

icon:check[] Core: A regression of creation of the named entities has been fixed.


icon:check[] Core: Improve the internal Java API of the list field creation, targeting better batch performance.


icon:check[] Core: Improve the internal Java API for granting and revoking permissions.


[[v2.0.10]]
== 2.0.10 (19.11.2023)

icon:check[] GraphQL: `referencedBy` field fetcher has been refactored for more optimal batch loading.

icon:check[] Tests: Added set of tests of uniqueness of the named entities on a database level.

icon:check[] Core: The cache internal Java API has been presented a new constructor, allowing using the weight instead of entity number for the cache size calculations, as well as some new statistics getters.

icon:check[] Core: Now caches treat NULL as a valid value, instead of a constant miss.

[[v2.0.9]]
== 2.0.9 (03.11.2023)

icon:check[] GraphQL: Some more multithreading issues with initialization of GraphQL have been fixed.


icon:check[] Core: Requests to branches failed with an internal error, if monitoring was disabled. This has been fixed.


icon:check[] Core: The new configuration option `vertxOptions.orderedBlockingHandlers` allows to change the behaviour of concurrent handling of "long running" requests
(requests that modify data or GraphQL requests). If the option is set to `true` (default value) such requests will be run in order (per http verticle) and never concurrently.
As a consequence, it may happen that e.g. GraphQL requests are queued for some time if some other requests are currently handled.
If the option is set to `false`, blocking requests will only be queued, if all threads of the worker pool are currently busy.


icon:check[] GraphQL: Performance optimizations of the Elasticsearch-based requests.


[[v2.0.8]]
== 2.0.8 (18.10.2023)

icon:check[] GraphQL: When the very first GraphQL Queries (after starting the Mesh instance) were executed in parallel, it could happen that
GraphQL execution failed with some internal errors. This has been fixed.


icon:check[] GraphQL: Parent loading has been speeded up by using a batch data loading.

icon:check[] Search: Minor logging changes in the search engine, making it less annoying.

[[v2.0.7]]
== 2.0.7 (04.10.2023)

icon:check[] Core: More NPE occurrences during the massive concurrent publishing process have been fixes.

[[v2.0.6]]
== 2.0.6 (20.09.2023)

icon:check[] Core: When running in the massive concurrent publishing process, it is possible to run into a race condition when some field containers are already processed while being referenced by the edge, 
throwing an NPE. This has now been fixed.


[[v2.0.5]]
== 2.0.5 (05.09.2023)

icon:check[] Mesh Rest Client: An error has been fixed, which prevented sorting parameters from being passed to the endpoint.


icon:check[] Clustering: Calling cluster specific REST Endpoints on non-clustered instances could cause internal server errors. The behaviour has been changed so that
a "Bad Request" error is returned containing a proper error message.


icon:check[] Java Rest Client: After logging in with the `login()` method, the login token was never refreshed, which caused it to expire after the configured token expiration time (per default 1 hour),
even if the client was used to do requests. This has been changed now, so that the login token in the client will be refreshed on every request to mesh.


icon:check[] GraphQL: Link resolving in graphql queries ignored the language tags in the links. This has been fixed.


icon:check[] GraphQL: The metadata request does not crash anymore on the empty (micro)schemas. The new related filter, `isEmpty`, has been added as well.


[[v2.0.4]]
== 2.0.4 (23.08.2023)

[[v2.0.3]]
== 2.0.3 (11.08.2023)

icon:check[] Java filter for Node reference content field has been fixed. Native filtering pagination has been improved. Some other minor stability fixed applied.

icon:check[] Plugins: Logging fixed upon false triggering of a warning of inexisting role/group connection.


icon:check[] Core: All named instances have been presented an own cache.


[[v2.0.2]]
== 2.0.2 (26.07.2023)

icon:check[] Core: Uniqueness checks for webroot url field values will now only be done, if those values actually change. This will improve performance of e.g. schema migrations, where the webroot url field values are likely to not change.


icon:check[] Core: An internal API for efficient loading of list field values has been added.


[[v2.0.1]]
== 2.0.1 (13.07.2023)

icon:check[] Clustering: Due to an incorrect check, it was possible that migration jobs could complete without actually migrating anything, when run in a clustered environment with disabled coordination mode.

[[v2.0.0]]
== 2.0.0 (29.06.2023)

icon:plus[] Core: Support of database level filtering/sorting has been added to the low level Java API.

icon:plus[] GraphQL: Support of database level filtering/sorting has been added. New `sort` parameter in added for structured sorting, forcing the usage of DB filtering. New GraphQL parameter `nativeFilter` 
is added to the selected entity lookup methods, with options `NEVER` (old filtering is forced), `ALWAYS` (DB filtering is forced), `IF_POSSIBLE` (if the requested filter is supported by a DB, DB filtering is used, otherwise filtering is fallen back to the old filter mechanism). 
Please note that not all the currently existing filters are supported by the DB.

icon:plus[] GraphQL: A simplified, native filtering friendly version of `regex` string operation, `like`, has been added, accepting wildcards `%` as a zeroable set of characters, e.g. `like: "hello%world"` requests filtering in the strings, that start with `hello`, end with `world` and have zero-to-unlimited number of any characters in between.

icon:plus[] GraphQL: Added new filters for field types: list, micronode, (s3)binary. Added a new experimental filter for referencedBy nodes.