Camunda Release Policy

Components of Camunda follow the Semantic Versioning standard, which defines a version number using the MAJOR.MINOR.PATCH pattern.

• MAJOR version can make incompatible changes to public API.
• MINOR version can add functionality in a backward-compatible manner.
• PATCH version can make backward-compatible bug fixes.

Standard Support Period

Camunda provides a standard support period of 18 months for Enterprise customers. Therefore, Camunda supports at least the last three released minor versions with patch releases. Patch releases are offered on a best-effort basis for currently supported versions.

Release Cadence

The Camunda team strives to release at least:

• Every six months (in April and October): a new minor version release.
• Every month: patch releases for all supported versions.
• In between minor versions: alpha releases to preview upcoming minor versions.

The Camunda team strives to release versions on the second Tuesday of the respective month.

What does "End of Maintenance" mean?

End of maintenance means that Camunda will not perform maintenance or release bug fixes and patch releases related to the version after the specified date. If you are planning to migrate to a newer version, see the Camunda 7 Update & Migration Guide or Camunda 8 Update Guide.

Please reach out if you have concerns or need help migrating to a newer version.

Why does Camunda change Supported Environments?

Camunda is committed to delivering improvements and bug fixes quickly while providing strong support across environments. As database and browser versions evolve, supporting a larger matrix of environments becomes increasingly difficult. Camunda no longer supports environments marked end-of-life by vendors, or very old versions that are no longer widely used.

Supported environments references:

• Camunda 7 Supported Environments
• Camunda 8 Supported Environments