@zapier/zapier-sdk 0.103.0 → 0.105.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +25 -0
- package/README.md +4 -2
- package/dist/{chunk-JJHKZ4XK.mjs → chunk-NF7CPRHH.mjs} +249 -129
- package/dist/{chunk-RHL6GGME.cjs → chunk-Y2OATBGZ.cjs} +249 -127
- package/dist/experimental.cjs +363 -355
- package/dist/experimental.d.mts +5 -3
- package/dist/experimental.d.ts +5 -3
- package/dist/experimental.mjs +2 -2
- package/dist/{index-DT4MnaD0.d.mts → index-DFhYYVH_.d.mts} +62 -5
- package/dist/{index-DT4MnaD0.d.ts → index-DFhYYVH_.d.ts} +62 -5
- package/dist/index.cjs +285 -277
- package/dist/index.d.mts +1 -1
- package/dist/index.d.ts +1 -1
- package/dist/index.mjs +1 -1
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,30 @@
|
|
|
1
1
|
# @zapier/zapier-sdk
|
|
2
2
|
|
|
3
|
+
## 0.105.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- ef3540d: Added `correlationId` and `causationId` options on `createZapierSdk`, matching
|
|
8
|
+
`--correlation-id` and `--causation-id` CLI flags, and the `ZAPIER_CORRELATION_ID`
|
|
9
|
+
and `ZAPIER_CAUSATION_ID` environment variables. When set, they are emitted as
|
|
10
|
+
`zapier-correlation-id` and `zapier-causation-id` headers on every outbound
|
|
11
|
+
Zapier API request. Precedence for both ids is: explicit option, then
|
|
12
|
+
environment variable, and for correlation the SDK falls back to its per-call
|
|
13
|
+
id so requests still carry a trace identifier. Precedence is: explicit option,
|
|
14
|
+
then environment variable. Empty strings at either layer are treated as unset.
|
|
15
|
+
|
|
16
|
+
## 0.104.0
|
|
17
|
+
|
|
18
|
+
### Minor Changes
|
|
19
|
+
|
|
20
|
+
- 1ec9410: SDK HTTP requests now automatically retry HTTP 500, 502, 503, and 504 responses for idempotent methods; HTTP 429 responses continue to retry for any method. All retryable responses share the budget set by `maxNetworkRetries`, with exponential backoff capped by `maxNetworkRetryDelaySeconds`; set `maxNetworkRetries: 0` to disable retries. Callers that pass a custom `sendHttpRequest` transport to `createZapierApi` remain responsible for its retry behavior.
|
|
21
|
+
|
|
22
|
+
### Patch Changes
|
|
23
|
+
|
|
24
|
+
- Updated dependencies [1ec9410]
|
|
25
|
+
- Updated dependencies [1ec9410]
|
|
26
|
+
- @zapier/kitcore@0.19.0
|
|
27
|
+
|
|
3
28
|
## 0.103.0
|
|
4
29
|
|
|
5
30
|
### Minor Changes
|
package/README.md
CHANGED
|
@@ -376,13 +376,15 @@ The `createZapierSdk(...)` factory function is the main entry point for the SDK.
|
|
|
376
376
|
| `debug` | `boolean` | ❌ | — | — | Enable debug logging. |
|
|
377
377
|
| `baseUrl` | `string` | ❌ | — | — | Base URL for Zapier API endpoints. |
|
|
378
378
|
| `trackingBaseUrl` | `string` | ❌ | — | — | Base URL for Zapier tracking endpoints. |
|
|
379
|
-
| `maxNetworkRetries` | `number` | ❌ | — | — | Max retries for rate-limited
|
|
380
|
-
| `maxNetworkRetryDelaySeconds` | `number` | ❌ | — | — | Max delay in seconds to wait
|
|
379
|
+
| `maxNetworkRetries` | `number` | ❌ | — | — | Max retries for rate-limited and server-error responses (default: 3). |
|
|
380
|
+
| `maxNetworkRetryDelaySeconds` | `number` | ❌ | — | — | Max delay in seconds to wait between network retries (default: 60). |
|
|
381
381
|
| `maxConcurrentRequests` | `number, literal` | ❌ | — | — | Max concurrent in-flight HTTP requests (default: 200, max: 10000). |
|
|
382
382
|
| `approvalTimeoutSeconds` | `number` | ❌ | — | — | Timeout in seconds for approval polling. Default: 600 (10 min). |
|
|
383
383
|
| `maxApprovalRetries` | `number` | ❌ | — | — | Maximum number of sequential approval rounds per request (one per gating policy) before giving up. Default: 2. |
|
|
384
384
|
| `approvalMode` | `string` | ❌ | — | `disabled`, `poll`, `throw` | Approval flow behavior for manual approvals. "poll" creates the approval, opens it in a browser, polls until resolved, and retries the original request. "throw" creates the manual approval and throws a ZapierApprovalError with the approval URL so the caller can surface it. Server-created auto-mode approvals always poll until they reach a terminal status and retry the original request on approval, even when this option is "throw". "disabled" throws a ZapierApprovalError on approval-required responses without creating an approval. Resolution order is: explicit option, then ZAPIER_APPROVAL_MODE, then the default behavior (poll for interactive TTY, throw otherwise). |
|
|
385
385
|
| `openAutoModeApprovalsInBrowser` | `boolean` | ❌ | — | — | By default, auto-mode approvals do not open in a browser. Enable this option to open the approval URL and watch the approval process. Resolution order is: explicit option, then ZAPIER_OPEN_AUTO_MODE_APPROVALS_IN_BROWSER, then false. |
|
|
386
|
+
| `correlationId` | `string` | ❌ | — | — | Correlation ID for request tracing. When set, emitted as the `zapier-correlation-id` header on every outbound request. Falls back to the ZAPIER_CORRELATION_ID environment variable. |
|
|
387
|
+
| `causationId` | `string` | ❌ | — | — | Causation ID for request tracing. When set, emitted as the `zapier-causation-id` header on every outbound request. Falls back to the ZAPIER_CAUSATION_ID environment variable. |
|
|
386
388
|
| `canIncludeSharedConnections` | `boolean` | ❌ | — | — | Allow listing shared connections. |
|
|
387
389
|
| `canIncludeSharedTables` | `boolean` | ❌ | — | — | Allow listing shared tables. |
|
|
388
390
|
| `canDeleteTables` | `boolean` | ❌ | — | — | Allow deleting tables. |
|