Preparation for gRPC: New Mandatory Properties

In preparation of replacement of the CORBA protocol by gRPC, new properties for all CMS components are required when using gRPC:

The Blueprint workspace is already equipped with all necessary properties. You may use those as examples on how to configure custom components and adjust your deployment.

(CMS-27662)

Supported: MySQL 8.4 on Amazon RDS

MySQL 8.4 on Amazon RDS has been added as a supported environment.

(CMS-27504)

Supported: PostgreSQL 16 on Azure

PostgreSQL 16 on Azure has been added as a supported environment.

(CMS-27503)

Support MySQL 8.4.

We now also support MySQL 8.4. No code change was required.

MySQL 8.4 replaces MySQL 8.0 as default for the Blueprint docker compose setup in the global/deployment/docker.

mysql-connector-j has also been updated to the latest version (9.2.0).

Support for MySQL 8.0 will be removed in future versions.

Please see https://dev.mysql.com/doc/refman/8.4/en/mysql-nutshell.html and https://dev.mysql.com/doc/refman/8.4/en/upgrading.html for more information on changes and upgrading.

(CMS-27308)

Support Oracle Database 23ai

We now also support Oracle Database 23ai.

The oracle driver com.oracle.database.jdbc:ojdbc11 has also been updated to the latest version (23.7.0.25.01).

Further, io.hypersistence:hypersistence-utils-hibernate-63 has been updated to the latest version (3.9.9).

When starting the applications against Oracle 23ai, a small schema update takes place that changes the type of a column in the notifications table to use Oracle’s new JSON type. Existing data is migrated automatically.

Support for Oracle Database 19c will be removed in future versions.

Please see https://docs.oracle.com/en/database/oracle/oracle-database/23/index.html for more information about versions and upgrading.

(CMS-27306)

Support PostgreSQL 16

We now also support PostgreSQL 16. No code change was required.

org.postgresql:postgresql has also been updated to the latest version (42.7.5).

Support for PostgreSQL 13 will be removed in future versions.

Please see https://www.postgresql.org/support/versioning/ for more information about versions and upgrading.

(CMS-27299)

Third-Party Update: Apache Solr 9.8.0

Apache Solr has been updated to version 9.8.0. The new version fixes security vulnerability CVE-2025-24814.

A new coremedia/solr-base Docker image with tag 2.5-cm-9.8.0 has been released, which also provides a fix for leader/follower replication with enabled basic authentication. It adds the environment variable SOLR_LEADER_BASIC_AUTH for configuring basic authentication credentials. Starting with previous release Solr 9.7.0, credentials that are included in the SOLR_LEADER_URL environment variable are not used anymore.

See https://solr.apache.org/docs/9_8_0/changes/Changes.html and https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html#solr-9-8 for a list of changes in Solr.

(CMS-27253)

Deprecation of Google Analytics Connectors

The integration of Google Analytics Connectors in Studio is deprecated together with the persistence based on the Elastic Core (ModelService). This includes extensions es-alx/es-alx-google, es-alx/es-alx-retrieval-component and module bpbase-es-alx-common. These features are discontinued and will be replaced by an integrated solution.

Update: Functionality for website tracking will still be available.

(CMS-25708)

MongoDB Persistence for Editorial Features has been Deprecated

MongoDB persistence for CapLists (My Edited Content and Workflow Lists), Notifications, and Projects/To-Dos will be removed in a future release. Please use SQL persistence instead.

Currently MongoDB persistence is still the technical default, but this will be replaced with the SQL persistence in a future release.

Find details how to enable the SQL persistence layer in the CoreMedia Blueprint Developer Manual in section “Blueprint Workspace for Developers/Configuring the Workspace”.

(CMS-25670)

Migration Support for Editorial Services from Elastic to SQL Persistence

With CMCC v12.2412.0.0 we introduced support for an SQL based persistence in favor of the MongoDB based persistence for these features:

Find details how to enable the SQL persistence layer in the CoreMedia Blueprint Developer Manual in section “Blueprint Workspace for Developers/Configuring the Workspace”.

Migration Support: With CMCC v12.2506.0.0 it is now possible to migrate existing data for these features from Elastic (MongoDB or In Memory) to the new SQL persistence, except for Notifications which will not be migrated.

(CMS-25656)

Added Escalation Info to Nagbar

Workflows escalations are shown in the overview and inside the nagbar of the workflow details view.

(CMS-25505)

Supported: PostgreSQL 16 on Amazon RDS

PostgreSQL 16 on Amazon RDS has been added as a supported environment.

(CMS-23960)

Removal of deprecated Commerce Capability Constants

The following deprecated commerce capability constants in com.coremedia.blueprint.base.livecontext.client.data.Capability were removed:

(CMS-23842)

Smart Validation for Segment in Commerce Pages

In commerce-related page types (Augmented Category, Augmented Product and Augmented Page) the segment is typically not used, at least when it is a commerce-led scenario. In such a case the segment is not used to build an URL (but it is a Storefront URL). Therefore, the segment does not need to be validated. Only in a hybrid scenario (when the settings "livecontext.policy.commerce-category-links", "livecontext.policy.commerce-product-links" or "livecontext.policy.commerce-page-links" are "true") the validation is done for these page types.

(CMS-18494)