@camunda8/orchestration-cluster-api 1.2.2 → 1.2.4-alpha.1

package/CHANGELOG.md

@@ -1,9 +1,28 @@
-## [1.2.2](https://github.com/camunda/orchestration-cluster-api-js/compare/v1.2.1...v1.2.2) (2025-12-01)
+## [1.2.4-alpha.1](https://github.com/camunda/orchestration-cluster-api-js/compare/v1.2.3...v1.2.4-alpha.1) (2026-01-22)
+
+### Bug Fixes
+
+- correctly type optional parameters ([8fef8c8](https://github.com/camunda/orchestration-cluster-api-js/commit/8fef8c8a4bc69a3dd86b76ac1e01431d97607050))
+- enhance response validation error message ([d138134](https://github.com/camunda/orchestration-cluster-api-js/commit/d1381348f46c187e8321fdec088b7654b70c4fa8))
+- handle multi-part spec ([86ac930](https://github.com/camunda/orchestration-cluster-api-js/commit/86ac930e3b599126cf5446bcaa323089049bb4ef))
+- **spec:** prevent path-local $like refs breaking dts build ([3b75200](https://github.com/camunda/orchestration-cluster-api-js/commit/3b75200caeffb198f072668567cff7e34f5700f0))
+
+### Features
 
+- build 8.9 from monorepo spec ([a80303d](https://github.com/camunda/orchestration-cluster-api-js/commit/a80303d3a54f2d6db77c428f46848f131bd8bf42))
+- build from 8.9 spec ([e4ab53c](https://github.com/camunda/orchestration-cluster-api-js/commit/e4ab53cd253ca5d1fcf2d0bf0626c8d26c7da49c))
+
+## [1.2.3](https://github.com/camunda/orchestration-cluster-api-js/compare/v1.2.2...v1.2.3) (2025-12-05)
+
+### Bug Fixes
+
+- support fetchVariables in job worker ([b672d8d](https://github.com/camunda/orchestration-cluster-api-js/commit/b672d8d3ec499624a58d1db2b8e920f3ccc77ebc))
+
+## [1.2.2](https://github.com/camunda/orchestration-cluster-api-js/compare/v1.2.1...v1.2.2) (2025-12-01)
 
 ### Bug Fixes
 
-* set default requestTimeout to 0 ([c18a22a](https://github.com/camunda/orchestration-cluster-api-js/commit/c18a22a0f5dacfcd6b16ac16d8260307a17f87d9))
+- set default requestTimeout to 0 ([c18a22a](https://github.com/camunda/orchestration-cluster-api-js/commit/c18a22a0f5dacfcd6b16ac16d8260307a17f87d9))
 
 ## [1.2.1](https://github.com/camunda/orchestration-cluster-api-js/compare/v1.2.0...v1.2.1) (2025-11-28)
 

package/README.md

@@ -114,7 +114,7 @@ Controlled by `CAMUNDA_SDK_VALIDATION` (or `config` override). Grammar:
 
 ```
 none | warn | strict | req:<mode>[,res:<mode>] | res:<mode>[,req:<mode>]
-<mode> = none|warn|strict
+<mode> = none|warn|strict|fanatical
 ```
 
 Examples:
@@ -398,6 +398,8 @@ const worker = client.createJobWorker({
   maxParallelJobs: 10,
   timeoutMs: 15_000, // long‑poll timeout (server side requestTimeout)
   pollIntervalMs: 100, // delay between polls when no jobs / at capacity
+  // Optional: only fetch specific variables during activation
+  fetchVariables: ['orderId'],
   inputSchema: Input, // validates incoming variables if validateSchemas true
   outputSchema: Output, // validates variables passed to complete(...)
   validateSchemas: true, // set false for max throughput (skip Zod)
@@ -416,6 +418,29 @@ process.on('SIGINT', () => {
 });
 ```
 
+Note on variable fetching:
+
+- `fetchVariables: string[]` limits variables returned on activated jobs to the specified keys. If omitted, all visible variables at activation scope are returned. This maps to the REST API field `fetchVariable`.
+
+TypeScript inference:
+
+- When you provide `inputSchema`, the type of `fetchVariables` is constrained to the keys of the inferred `variables` type from that schema. Example:
+
+```ts
+const Input = z.object({ orderId: z.string(), amount: z.number() });
+client.createJobWorker({
+  jobType: 'process-order',
+  maxParallelJobs: 5,
+  jobTimeoutMs: 30_000,
+  inputSchema: Input,
+  // Only allows 'orderId' | 'amount' here at compile-time
+  fetchVariables: ['orderId', 'amount'],
+  jobHandler: async (job) => job.complete(),
+});
+```
+
+- Without `inputSchema`, `fetchVariables` defaults to `string[]`.
+
 ### Job Handler Semantics
 
 Your `jobHandler` must ultimately invoke exactly one of: