Skip to main content
Version: 8.8 (unreleased)

Release announcements

Supported environment changes and breaking changes or deprecations for the Camunda 8.7 release are summarized below.

Scheduled release dateScheduled end of maintenanceRelease notesBlog
8 April 202513 October 20268.7 release notesAnnouncing Camunda 8.7
Release notes and quality board
  • See release notes to learn more about new features and enhancements.
  • Refer to the quality board for an overview of known bugs by component and severity.

Changes in supported environments​

Identity Keycloak now requires v25 or v26 Self-Managed​

Identity 8.7 now requires Keycloak v25 or v26, and Keycloak versions must be updated to match. This update also includes changes to the Camunda Helm chart. For more information on configuration changes, see the Self-Managed update guide.

Spring Zeebe SDK now requires Spring Boot 3.4.x SaaSSelf-Managed​

The Spring Zeebe SDK 8.7 now requires Spring Boot 3.4.x. For more information on compatibility, see the Spring Zeebe SDK version compatibility matrix.

Desktop Modeler no longer supports macOS 12​

Following the end-of-life of macOS 12, support for Desktop Modeler on macOS 12 has been removed.

Key changes​

Deprecation of Self-Managed AWS Marketplace offering​

As of October 2025, the Self-Managed AWS Marketplace offering will be deprecated and no longer publicly available.
Existing customers may continue to use the product until their contracts expire.

For future use, refer to our new AWS Marketplace listing for more information.

Deploy diagram change Self-Managed​

With this version, we ship a breaking change to how Web Modeler Deploy diagram modals work. Clusters must now be proactively configured to be able to deploy from Web Modeler.

New 8.7 deploy diagram modal
  • In 8.6, you could still configure cluster details on the Deploy diagram modal when deploying.
  • In 8.7, you can no longer configure cluster details on the Deploy diagram modal. You must configure the cluster to be able to deploy from this modal.
  • Note that you must also be assigned the Zeebe Identity role to be able to deploy (if BEARER_TOKEN is used as authentication).

Deprecated: Web Modeler cluster authentication OAUTH and CLIENT_CREDENTIALS Self-Managed​

The following authentication methods for a configured cluster in Web Modeler are now being deprecated and will no longer be supported in version 8.8:

  • OAUTH: This method was replaced by BEARER_TOKEN.
  • CLIENT_CREDENTIALS: This method was introduced as a temporary solution to support deployments from Web Modeler when using Microsoft Entra ID or a generic OIDC provider. It is marked for removal in 8.8 as the BEARER_TOKEN authentication will be supported for Entra ID and generic providers as well.

Breaking changes in Camunda Process Test​

In version 8.6, the element assertions use names to identify the BPMN elements. Starting with version 8.7, the element assertions use BPMN element IDs instead of names. This change eases the migration of previous testing frameworks and aligns with other APIs.

If you prefer to stay with element names, you can use the new element selector io.camunda.process.test.api.assertions.ElementSelectors#byName.

To migrate all your test cases at once, change the default element selector in the configuration.

Deprecated: OpenAPI entities with integer (int64) key attributes​

OpenAPI entities containing keys of type integer (int64) are now being deprecated. This is part of a transition where API entity keys change from type integer (int64) to string.

See the overview about API Key Attributes for more details.

Zeebe Java client​

Starting with 8.8, the Zeebe Java client will become the new Camunda Java client. This transition brings a new Java client structure designed to enhance the user experience and introduce new features while maintaining compatibility with existing codebases.

The primary goal of those changes is to enable users to interact with Camunda clusters with one consolidated client rather than multiple. The CamundaClient will replace the ZeebeClient, offering the same functionality and adding new capabilities.

If you need to continue using the old ZeebeClient, you can use the new version 8.8 CamundaClient artifact without issues as it still contains the related ZeebeClient classes. Those classes are marked as deprecated, so you can easily spot code you need to adjust to the CamundaClient.

The old zeebe-client-java artifact will be relocation-only, so your build system is redirected to the new camunda-client-java artifact. We will discontinue the old artifact with a future release and recommend using the new one.

note

The Zeebe Java client will not be developed further and will only receive bug fixes for as long as version 8.7 is officially supported.

Spring Zeebe SDK​

Starting with 8.8, the Spring Zeebe SDK will become the new Camunda Spring Boot SDK. The SDK will rely on the new Camunda Java client, designed to enhance the user experience and introduce new features while maintaining compatibility with existing codebases.

note

The Spring Zeebe SDK will not be developed further and will only receive bug fixes for as long as version 8.7 is officially supported.

Camunda 8 Self-Managed​

Helm​

Separated Ingress deprecation​

The separated Ingress Helm configuration for Camunda 8 Self-Managed has been deprecated in 8.6, and will be removed from the Helm chart in 8.8. Only the combined Ingress configuration is officially supported. See the Ingress guide for more information on configuring a combined Ingress setup.

ExtraVolumeClaimTemplates​

You can now add custom extraVolumeClaimTemplates to the Zeebe/Core StatefulSet by supplying an array of templates in your Helm values file. This allows you to attach additional persistent volumes to each Zeebe/Core pod for use cases such as custom storage or log directories.

Important:
Kubernetes does not allow you to change the volumeClaimTemplates of an existing StatefulSet. If you add, remove, or modify extraVolumeClaimTemplates after initial deployment, you must delete and recreate the StatefulSet (which will also delete the pods) for the changes to take effect. This may require additional planning and data migration steps to avoid data loss.

Common labels for Camunda resources​

A new commonLabels value is now available and integrates with camundaPlatform.labels. This allows you to define mutable labels that are automatically applied to all Camunda resources. By setting commonLabels, you can ensure consistent labeling across deployments, making it easier to manage, organize, and identify resources within your Camunda environment.

Configure Web Modeler replicas​

The number of replicas for the Web Modeler REST API and web app deployments can be set with new configuration properties: webModeler.restapi.replicas and webModeler.webapp.replicas, respectively.

External database for Web Modeler REST API​

The configuration for the external database used by the Web Modeler REST API has been updated to align with the Identity component's database configuration. A new value, webModeler.restapi.externalDatabase, is now available and mirrors the structure of identity.externalDatabase. To ensure backward compatibility, the existing webModeler.restapi.externalDatabase.url field is retained and will take precedence if set.

Adjustments​

  • New package structure:
    • Package io.camunda.client: This package contains the new CamundaClient and all the features slated for release in version 8.8.
  • Properties and environment variables refactoring:
    • All old Java client property names will be refactored to more general ones. For instance, zeebe.client.tenantId will become camunda.client.tenantId.
    • Similarly, environment variables will be renamed following the same concept: ZEEBE_REST_ADDRESS will become CAMUNDA_REST_ADDRESS.
  • Artifact ID change:
    • The artifactId will change from zeebe-client-java to camunda-client-java.

Connectors​

Starting with 8.7, the connector runtime will stop using the deprecated community Spring Zeebe library to communicate with the core APIs of Camunda. The new Spring Zeebe SDK will be used instead.

Although the official SDK is largely compatible with the community library, some changes might be required in the configuration of Self-Managed connector deployments.

We recommend updating the configuration to match the new property format of the Spring Zeebe SDK to avoid any issues. The old properties will be removed in a future release.

For more information, see the update guide and the connectors configuration guide.