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 a very recent upstream push on 2026-08-31 and multiple follow-on updates in 2026, including alpha updates and numbered versions.
- Apparent update cadence is fairly steady, with frequent changes through mid 2026 (for example, late June to late August includes several
v8.9.0-alpha.*updates), suggesting an ongoing development rather than a long freeze.
AI summary generated
Recent updates
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.
Featuresv8.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.
Featuresv8.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.
SecurityFeaturesv8.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.
Featuresv8.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).
Securityv8.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.
Featuresv8.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.
Featuresv8.8.9
v8.8.9 release notes mention a single bug fix: keeping `error.message` static to improve error-monitoring grouping. The actual diff for this release contains additional behavioral and public API changes that are not mentioned, including worker streaming/polling logic, gRPC stream timeout handling, and a change in the return type of variable parsing.
BreakingFeatures