Back to Explore

camunda/camunda-8-js-sdk

GitHub
11 updates · last 90 daysOpen source

Last release:

The Camunda 8 JavaScript SDK for Node.js, written in TypeScript, provides API clients for Camunda Platform 8. It is useful for integrating Camunda 8 orchestration via the Orchestration Cluster API, with strongly typed (strict) and string-based (loose) client options.

Project status

  • Actively maintained, with an upstream push and multiple updates on November 3, 2026.
  • Updates have been frequent recently, including several in one day, though the evidence does not establish a regular cadence.

AI summary generated

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • v8.8.20

    v8.8.20 fixes slow backlog processing in `ZBStreamWorker`: after processing a full batch, the worker polls again immediately instead of waiting for the next poll interval. The drain waits for handlers to settle before activating another batch, limiting in-flight activated jobs.

  • v8.8.19

    v8.8.19 fixes dead `streamJobs` streams by detecting stream failures and recovering through reconnection. The code also adds configurable recovery callbacks and backoff behavior, refreshes the lockfile, and changes CI formatting and conflict-marker checks.

    Features
  • v8.9.0-alpha.17

    This release fixes stream-worker backlog draining so jobs continue to be processed instead of waiting for the next poll interval after one batch. The code also adds a shared gRPC stream lifecycle API, including observable stream handles and lifecycle state, changes not described in the release notes.

    Features
  • v8.9.0-alpha.16

    The release notes document a fix for detecting and recovering from dead job streams in Zeebe streamJobs. The diff also shows substantial undocumented work, including an HTTP transport migration, new Admin API operations, document upload changes, and updates for nullable REST response fields.

    Features
  • v8.8.18

    v8.8.18 primarily continues the migration from got to an undici-based HTTP stack for REST calls. The code diff also shows additional public surface changes (new exports and new AdminApiClient operations) and substantial internal refactoring around multipart uploads and HTTP client behavior.

    Features
  • v8.9.0-alpha.15

    v8.9.0-alpha.15 replaces the SDK's got@11-based REST layer with an undici-based HTTP client (plus a got-compatible API surface) for all REST calls. The diff also introduces a new multipart upload pipeline that converts streams to Blobs, with MIME type inference and improved streaming behavior.

    BreakingFeatures
  • v8.8.17

    Release v8.8.17 primarily documents a fix for a crash caused by REST retries on Node.js >= 24.20. The code diff shows that while this workaround was added, several other API and behavior changes were also introduced, including new public exports, Admin/Modeler/OAuth functionality additions, and changes to error reporting and certificate handling.

    Breaking
  • v8.9.0-alpha.14

    v8.9.0-alpha.14 ships a fix for a Node.js >= 24.20 issue where got 11 retry behavior could crash the process. The main code change introduces a custom got request function and wires it into the SDK HTTP clients, alongside adding coverage via a new unit test.

  • v8.9.0-alpha.13

    Release v8.9.0-alpha.13 is documented as a pair of bug fixes. It targets the Web Modeler API to allow deleting projects that contain process applications, and it updates Windows system certificate retrieval to use Node's native tls.getCACertificates instead of node-forge.

    Security
  • v8.9.0-alpha.12

    v8.9.0-alpha.12 primarily fixes Zeebe job streaming issues: caller-supplied tenantIds are forwarded during activateJobs, failed job completion commands now propagate as errors, and the ZBStreamWorker no longer leaks one timer per sidecar poll cycle. The code diff also includes additional robustness changes in the stream worker and an undocumented delay in the process-cancellation helper.

  • v8.9.0-alpha.11

    v8.9.0-alpha.11 is a small release with a single documented bug fix for the Modeler client. The change ensures that if CAMUNDA_MODELER_BASE_URL contains a query string, that query is preserved correctly across subsequent requests.

  • v8.8.13

    Release v8.8.13 primarily updates the Web Modeler API integration by adding the newer versions endpoints and deprecating milestone endpoints. It also fixes the modeler delete methods to resolve with a real null value instead of a casted placeholder.

    Features
  • v8.9.0-alpha.10

    v8.9.0-alpha.10 adds Modeler “versions” API support and deprecates the older “milestones” API for Web Modeler 8.9 and later. It also fixes how delete-like methods resolve their return values, so they return real null instead of a cast.

    Features
  • v8.9.0-alpha.9

    v8.9.0-alpha.9 documents a single change, adding the ability to override the REST client retry configuration via a constructor option. The actual code diff includes several additional changes across Admin API, OAuth token handling hardening, gRPC streaming timeout behavior, and error formatting/logging that are not mentioned in the release notes.

    SecurityFeatures
  • v8.8.12

    v8.8.12 mainly documents a change in the rest-client to allow overriding HTTP retry configuration via a constructor option. The actual diff for this release is substantially broader, touching REST, OAuth token handling, gRPC streaming, worker polling behavior, and error formatting, with many changes not mentioned in the release notes.

    Features
  • v8.9.0-alpha.8

    v8.9.0-alpha.8 is a small release that claims a bug fix related to Slack/community notifications by passing the PR author association. The actual code changes are limited to CI/workflow configuration plus version metadata.

  • v8.9.0-alpha.7

    v8.9.0-alpha.7 contains a small bug fix related to Zeebe worker polling behavior, plus extensive CI and repository maintenance changes. The release notes only mention “issue 784” without describing the concrete runtime behavior change. Code changes also include dependency lockfile updates and some test/CI adjustments that are not described in the release notes.

  • v8.8.11

    v8.8.11 primarily hardens OAuth disk token caching. It changes how cached OAuth tokens are written to disk to restrict file permissions to the current user only (mode 0600).

    Security
  • v8.9.0-alpha.6

    Release v8.9.0-alpha.6 documents an Admin API expansion (implementing missing admin operations) and several OAuth reliability and error-monitoring improvements. The provided release notes do not mention multiple Zeebe runtime and API helper changes that are present in the actual diff.

    Features
  • v8.8.10

    Release v8.8.10 focuses on reliability improvements to OAuth handling and adds the remaining missing Admin API operations. It also includes a test adjustment for 403 detection and several internal code and type definition cleanups.

    Features