We’ve published two releases today.
Operaton 2.1.5
A routine maintenance release: dependency updates across the Maven and npm
dependency tree, a fix for German-language password-related UI text in the
web apps, and CI/build stability improvements. No database schema changes,
no REST API changes — a drop-in upgrade from any 2.1.x version.
Release notes: 2.1 | Operaton Documentation
GitHub release: Release v2.1.5 · operaton/operaton · GitHub
Operaton 2.2.0-RC1
The first release candidate for the upcoming 2.2 line — a preview build for
early testing, not intended for production. Highlights:
- New Webapps — The Operaton team (especially @paul owns the kudos!) is working on a replacement of the legacy Camunda CE webapps. With this release, the new webapps (codename “Webapps Neo”) are ready to be tested by the public.
- Spring Boot 4.1 upgrade — brings in the latest Spring Framework improvements and dependency baselines. Existing 2.1 Spring Boot apps should migrate smoothly.
- WildFly 40 & CDI 4.1 — process application WARs no longer need a
jboss-deployment-structure.xmlon WildFly 39+. - Nullability declarations in the engine API — engine internals are now incrementally annotated with JSpecify
@Nullable/@NonNull, making nullability contracts explicit and tool-checkable. See our forum post on the approach. - FEEL engine unshaded — resolves duplicate-class conflicts between the engine’s bundled dependencies and an application’s own classpath.
- Security: pinned vulnerable transitive Netty/Jackson versions still managed by current Quarkus/Spring Boot platforms.
- Task authorization query performance — task list/count queries now use an
EXISTSsubquery instead of a join, avoiding inflated intermediate result sets under high load.
Release notes (updated as 2.2 progresses toward GA): 2.2 (DRAFT) | Operaton Documentation
GitHub release (prerelease): Release v2.2.0-RC1 · operaton/operaton · GitHub
Feedback on the RC is very welcome here on the forum or on Slack!