id | title | description |
---|---|---|
announcements |
Announcements |
Important announcements including deprecation & removal notices |
Release date: 11th of October 2022
End of maintenance: 10th of April 2024
:::caution
The Zeebe release 8.1.23
suffers from camunda/zeebe#16406, which results in a Zeebe broker being unable to start if at least one DMN Model is deployed. We urge users to skip this release and update to 8.1.24
right away.
:::
Release date: 12th of April 2022
End of maintenance: 11th of October 2023
The Camunda 8.0.15
release pipeline lead to corrupted Zeebe 8.0.15
artifacts getting published.
The whole Camunda 8.0.15 release was thus skipped and updates from Camunda 8.0.14
should go straight to Camunda 8.0.16
.
The DeployProcess RPC was deprecated in 8.0. It is replaced by the DeployResource RPC.
The zeebe-test
module was deprecated in 1.3.0. We are currently planning to remove zeebe-test
for the 1.4.0 release.
The support for YAML processes was removed as of release 1.0. The resourceType
in Deployment record and Process grpc request are deprecated; they will always contain BPMN
as value.
YAML workflows are an alternative way to specify simple workflows using a proprietary YAML description. This feature is deprecated and no longer advertised in the documentation. YAML workflows gained little traction with users and we do not intend to support them in the future.
We recommend all users of YAML workflows to migrate to BPMN workflows as soon as possible. The feature will eventually be removed completely, though the date when this will occur has yet to be defined.
- TOML configuration - deprecated and removed in 0.23.0-alpha2
- Legacy environment variables - deprecated in 0.23.0-alpha2, removed in 0.25.0
New configuration:
exporters:
elasticsearch:
className: io.camunda.zeebe.exporter.ElasticsearchExporter
debughttp:
className: io.camunda.zeebe.broker.exporter.debug.DebugHttpExporter
In terms of specifying values, there were two minor changes:
- Memory sizes are now specified like this:
512MB
(old way:512M
) - Durations (e.g. timeouts) can now also be given in ISO-8601 Durations format. However, you can still use the established method and specify a timeout of
30s