← Back to all sparks
Z

Zeebe

DEVOPS
Velocity5.0

Distributed workflow engine for microservice orchestration

Camunda's 8.10 alpha threads business IDs through the stack while the tag feed fills with CI noise.

workflow-orchestrationbusiness-idmonorepo-tagsbackportsapi-surface
Current state
Zeebe's public tag stream is dominated by monorepo automation: renovate dependency bumps, backport tags and CI hardening published as `0.0.0-dryrun-*` releases. The substantive work sits in the 8.10.0-alpha4 line, where late business ID assignment landed across the engine, REST, gRPC and the Java client at once. Maintenance branches 8.7 through 8.9 continue to take security and stability backports in parallel.
Where it's heading
Camunda is building 8.10 as a correlation-identity release: business IDs propagate from job completion through the engine into secondary storage, which is the groundwork for tracing a process instance by a domain key rather than an internal one. The alpha4 line has now moved from rc1 through rc2 to a full alpha with the same feature set, so the surface is stabilising rather than expanding. Four supported branches receiving concurrent backports signals the enterprise support burden is shaping release cadence as much as new capability.
Prediction
Expect 8.10.0-alpha5 or a beta that consolidates the business ID surface and starts exercising it in Operate and Tasklist queries. Whether anything beyond business IDs is targeted for 8.10 is not visible in these entries.

Recent moves

  1. 6d ago

    Webapp client picks up TanStack router patch bumps

    A renovate-generated dry-run tag carrying TanStack router patch bumps for the webapp client. It is build automation surfacing in the release feed, not a change to the orchestration engine.

    View source ↗
  2. 6d ago

    Alpha-channel twin of the same dependency bump tag

    The alpha-channel twin of the same dependency dry-run tag, published in the same second with an identical body. One dependency update, emitted twice by the monorepo's tagging automation.

    View source ↗
  3. 8d ago

    Backport to 8.9: release the backup store on retention change

    A backport to the 8.9 maintenance branch releasing the backup store when retention changes. Operationally sensible for long-running clusters, but invisible to anyone modelling processes.

    View source ↗
  4. 8d ago

    Skip memory-leaking Operate history panel tests on 8.8

    Test housekeeping on 8.8: leaking Operate history panel tests are skipped rather than fixed, with the underlying refactor explicitly deferred. A note about technical debt, not a shipped change.

    View source ↗
  5. 9d ago

    CI: block the pull_request_target trigger on 8.7

    A CI security fix backported to 8.7, denying the pull_request_target trigger. It closes a build-pipeline exposure and changes nothing about the product itself.

    View source ↗
  6. 13d ago

    8.10 alpha: business IDs reach the engine, APIs and FEEL

    The alpha4 release consolidates late business ID assignment across the job-completion API, engine processing, forward-propagation semantics and exporters into secondary storage. It is the substance behind the 8.10 line and the payoff of the rc1 and rc2 candidates that preceded it, extending an identity concept rather than opening a new capability surface.

    View source ↗