Third-Party Update: Zookeeper 3.9.6

Apache Zookeeper has been updated to 3.9.6.

(CMS-31779)

Set OCI image format for single-arch build and add missing multi-arch profile to management-tools image build

All application image maven pom files use the OCI format for single-arch build and docker format for multi-arch build.

The management-tools image missed that change.

It is important to note, that it is currently not possible to push multi-arch index files with the OCI format due to a bug in the Jib plugin code.

(CMS-31431)

Third-Party Update: Apache Tika 3.3.2 and Transitive Dependencies

Apache Tika has been updated to version 3.3.2. As part of this change, transitive dependencies of Apache Tika have been updated.

Updated dependencies:

If you use these libraries in project code, please check their respective release notes for changes and upgrade information.

(CMS-31208)

CAE can serve an llms.txt file for each site

The CAE can now serve an llms.txt file for each site, following the community specification at https://llmstxt.org/. This lets editors provide large language models (LLMs) and AI-based tools (chat assistants, coding agents, AI-powered search) with concise, curated guidance about a site's content, instead of relying on them to crawl and parse the full HTML. The CAE supports only top-level llms.txt files, no specific llms.txt files for paths within a site.

Editors provide the file's content by a CMDownload content named “llms.txt”, placed next to the site indicator content. The content's data must be plain text or Markdown. Providing this content is entirely optional — if none exists for a site, the CAE serves a 404 response for that site's llms.txt.

Because llms.txt must be reachable at the top level of a site's domain (e.g. https://www.example.com/llms.txt), the reverse proxy in front of the CAE needs to route requests for that path to the CAE's internal handler.

For details, see the Blueprint Developer Manual, section “CoreMedia Blueprint - Functionality for Websites“ / “Website Management” / “LLMs File”.

(CMS-30563)

Protect the rights of configured groups in Studio

The new property studio.usermanager.rights-protected-group-names names groups whose rights must not be changed from Studio. Their access control rules are no longer offered for editing, neither in the user manager nor in the permissions tab of a folder's properties dialog, and their administrative flag cannot be changed, so that none of these rights can be modified or deleted accidentally. Apart from their rights, these groups stay editable as usual.

This is a convenience guard for Studio users, not a security boundary: the rights can still be changed with the Unified API and the command line tools.

In 2406.4 the property is named studio.usermanager.rightsProtectedGroupNames, which is the only spelling accepted in that version. It stays valid in later versions, so an existing 2406.4 configuration does not have to be changed when upgrading.

For details see the Studio Developer Manual, section "User Manager".

(CMS-25673)