# @zapier/zapier-sdk-mcp ## 0.21.9 ### Patch Changes - Updated dependencies [8ab4e96] - @zapier/zapier-sdk@0.103.0 ## 0.21.8 ### Patch Changes - Updated dependencies [2c8ea56] - @zapier/zapier-sdk@0.102.4 ## 0.21.7 ### Patch Changes - Updated dependencies [4a51b07] - @zapier/zapier-sdk@0.102.3 ## 0.21.6 ### Patch Changes - Updated dependencies [b6dfdf9] - @zapier/zapier-sdk@0.102.2 ## 0.21.5 ### Patch Changes - Updated dependencies [173df80] - @zapier/zapier-sdk@0.102.1 ## 0.21.4 ### Patch Changes - Updated dependencies [52b672a] - @zapier/zapier-sdk@0.102.0 ## 0.21.3 ### Patch Changes - Updated dependencies [6bfea6d] - @zapier/zapier-sdk@0.101.2 ## 0.21.2 ### Patch Changes - Updated dependencies [e0fcb04] - @zapier/zapier-sdk@0.101.1 ## 0.21.1 ### Patch Changes - Updated dependencies [cfc7020] - @zapier/zapier-sdk@0.101.0 ## 0.21.0 ### Minor Changes - 22a885c: Added `validate-workflow` (experimental) as an MCP tool for checking durable workflow source without publishing it. Returns an `issues` array of source diagnostics, empty when the source is valid. ### Patch Changes - Updated dependencies [22a885c] - @zapier/zapier-sdk@0.100.0 ## 0.20.5 ### Patch Changes - Updated dependencies [9cde1f6] - @zapier/zapier-sdk@0.99.0 ## 0.20.4 ### Patch Changes - Updated dependencies [cd0616e] - @zapier/zapier-sdk@0.98.1 ## 0.20.3 ### Patch Changes - Updated dependencies [9a5ae37] - @zapier/zapier-sdk@0.98.0 ## 0.20.2 ### Patch Changes - Updated dependencies [e45f03b] - @zapier/zapier-sdk@0.97.1 ## 0.20.1 ### Patch Changes - Updated dependencies [abbeb60] - @zapier/zapier-sdk@0.97.0 ## 0.20.0 ### Minor Changes - 2726599: Added `create-form` (experimental) as an MCP tool for creating Zapier Forms from a title and optional fields. Forms publish by default and return a shareable `hosted_url`. ### Patch Changes - Updated dependencies [2726599] - @zapier/zapier-sdk@0.96.0 ## 0.19.2 ### Patch Changes - Updated dependencies [80dc74a] - Updated dependencies [6e5189c] - @zapier/zapier-sdk@0.95.0 ## 0.19.1 ### Patch Changes - Updated dependencies [59a8180] - @zapier/zapier-sdk@0.94.1 ## 0.19.0 ### Minor Changes - d700196: Added `createActionRun` and `getActionRun`, the two halves of `runAction` as separately callable methods: - `createActionRun({ app, actionType, action, connection?, inputs?, page?, callbackUrl? })` — starts an action run and returns `{ id, implementation_id }` right away, without waiting for it to finish. `implementation_id` is the versioned implementation the run was started against, matching `implementation_id` on an app from `getApp` / `listApps`. - `getActionRun({ run })` — returns that run's state: `{ id, status, results, errors, next_page? }`. It is a point-in-time read that answers immediately, so a run that is still executing comes back with `status: "waiting"` and it is up to the caller to check again. Unlike `runAction`, a failed run is reported as `status: "error"` with the details in `errors` rather than thrown. To page a bulk read, pass the `next_page` from `getActionRun` back as the `page` for the next `createActionRun`. The pair uses the same page terminology in both directions, and `next_page` is always a string so it can be handed straight back. `runAction` is a paginated list method, so it keeps the SDK's usual `cursor` / `nextCursor` pair. Pass `callbackUrl` to `createActionRun` to skip polling altogether: Zapier posts the finished run to that URL. It must use HTTPS and resolve to a public host. The delivered body matches what `getActionRun` returns, and carries a `Zapier-Callback-Signature` header holding an RS256 JWT you can verify against `https://zapier.com/.well-known/jwks.json`. Delivery is retried, so the same run can arrive more than once. `runAction` is unchanged and is still the right call for most cases — it starts a run and waits for the result in one step. Reach for the pair when you don't want to block on the result: fan out many runs and collect them later, hand a run ID to another process, or pick a run back up after a restart. Run results are retained for seven days. ### Patch Changes - Updated dependencies [d700196] - @zapier/zapier-sdk@0.94.0 ## 0.18.23 ### Patch Changes - Updated dependencies [bc7405e] - @zapier/zapier-sdk@0.93.0 ## 0.18.22 ### Patch Changes - Updated dependencies [67db455] - @zapier/zapier-sdk@0.92.1 ## 0.18.21 ### Patch Changes - Updated dependencies [87e634f] - Updated dependencies [56f0789] - @zapier/zapier-sdk@0.92.0 ## 0.18.20 ### Patch Changes - Updated dependencies [4886b5b] - @zapier/zapier-sdk@0.91.1 ## 0.18.19 ### Patch Changes - 5935b7e: Added `publishWorkflowDraft` (experimental) to publish an open workflow draft as a new immutable version. - Publishing advances the workflow's live pointer and **discards the draft** — publish consumes it, so an open draft always means unpublished work. Returns both the new `version` and the consumed `draft` (`status: "discarded"`, `base_version_id` still recording the version it was forked from). Prefer it over `publishWorkflowVersion` once a draft exists, so the open draft is never orphaned; continue editing by creating a new draft off the new version. - Accepts optional `enabled` (set the workflow's enabled state as part of the publish; preserved if omitted) and `draftRevision` (optimistic concurrency: publish exactly the revision last read). - Failure modes stay distinct: a concurrent-edit or trigger-switchover conflict surfaces as `ZapierConflictError` (retryable after re-reading the draft), a trigger-catalog validation outage surfaces as a retryable 503 API error, and invalid `zapier_durable_version` or trigger config surfaces as a validation error. - Updated dependencies [5935b7e] - @zapier/zapier-sdk@0.91.0 ## 0.18.18 ### Patch Changes - f6eac6f: Added `createWorkflowDraft`, `updateWorkflowDraft`, and `discardWorkflowDraft` (experimental), completing the draft lifecycle alongside the existing read methods. - `createWorkflowDraft` forks a new draft from the workflow's live version, with an optional `slug`. - `updateWorkflowDraft` saves draft edits — source files, dependencies, trigger, connections, and app-version pins. Pass `draftRevision` to reject the save with a `ZapierConflictError` if the draft changed since it was last read; pass `null` for `trigger`, `connections`, or `appVersions` to clear the stored value, or omit them to leave it unchanged. - `discardWorkflowDraft` soft-deletes a draft and returns it with status `discarded`. All ID inputs are UUID-validated at the boundary. - Updated dependencies [f6eac6f] - @zapier/zapier-sdk@0.90.0 ## 0.18.17 ### Patch Changes - e24c236: Added `listWorkflowDrafts` and `getWorkflowDraft` (experimental). `listWorkflowDrafts` is paginated (cursor + pageSize), returns a workflow's drafts most recently edited first, and filters by `status` (server default: open) or exact `slug`. `getWorkflowDraft` returns the full draft state including `source_files` and `draft_revision`, the draft's optimistic-concurrency counter. CLI commands taking a draft id present an interactive picker. All ID inputs are UUID-validated at the boundary. - Updated dependencies [e24c236] - @zapier/zapier-sdk@0.89.0 ## 0.18.16 ### Patch Changes - Updated dependencies [60892be] - @zapier/zapier-sdk@0.88.1 ## 0.18.15 ### Patch Changes - Updated dependencies [0e49ffa] - @zapier/zapier-sdk@0.88.0 ## 0.18.14 ### Patch Changes - Updated dependencies [920d571] - @zapier/zapier-sdk@0.87.1 ## 0.18.13 ### Patch Changes - 4e560c0: The MCP server now handles approval-required errors correctly, returning the approval URL or denial reason instead of a generic error. Previously an `instanceof` check failed across bundled copies of the SDK, so approvals fell through to generic error handling. - Updated dependencies [4e560c0] - @zapier/zapier-sdk@0.87.0 ## 0.18.12 ### Patch Changes - Updated dependencies [afa9c95] - @zapier/zapier-sdk@0.86.0 ## 0.18.11 ### Patch Changes - Updated dependencies [769751e] - @zapier/zapier-sdk@0.85.0 ## 0.18.10 ### Patch Changes - Updated dependencies [840aca3] - @zapier/zapier-sdk@0.84.4 ## 0.18.9 ### Patch Changes - Updated dependencies [e6b22fb] - @zapier/zapier-sdk@0.84.3 ## 0.18.8 ### Patch Changes - Updated dependencies [e1c327d] - @zapier/zapier-sdk@0.84.2 ## 0.18.7 ### Patch Changes - Updated dependencies [197a125] - @zapier/zapier-sdk@0.84.1 ## 0.18.6 ### Patch Changes - e1896a3: Code Substrate methods now use the `/code-substrate-runner` and `/code-substrate-workflows` API path prefixes across the SDK, the CLI, and the MCP server, and `sdk.context.api` and the CLI `curl` command accept paths built on them. The previous `/sdkdurableapi` and `/durableworkflowzaps` prefixes remain supported. - Updated dependencies [e1896a3] - @zapier/zapier-sdk@0.84.0 ## 0.18.5 ### Patch Changes - Updated dependencies [90ac367] - @zapier/zapier-sdk@0.83.3 ## 0.18.4 ### Patch Changes - Updated dependencies [bf0d056] - @zapier/zapier-sdk@0.83.2 ## 0.18.3 ### Patch Changes - Updated dependencies [6201fd4] - @zapier/zapier-sdk@0.83.1 ## 0.18.2 ### Patch Changes - 5f5f028: Fixed: `experimental: true` now registers the experimental (trigger) tools. The server previously built the stable SDK regardless of the flag. - Updated dependencies [5f5f028] - @zapier/zapier-sdk@0.83.0 ## 0.18.1 ### Patch Changes - Updated dependencies [ce612ee] - @zapier/zapier-sdk@0.82.1 ## 0.18.0 ### Minor Changes - d09592b: Graduated Triggers and Trigger Inbox methods from the experimental interface to the stable one. Every trigger method (`listTriggers`, `listTriggerInputFields`, `createTriggerInbox`, `ensureTriggerInbox`, `drainTriggerInbox`, `watchTriggerInbox`, the inbox lifecycle methods, and the message lease/ack/release methods) is now available directly from `@zapier/zapier-sdk` and the `zapier-sdk` CLI — no `/experimental` import, `--experimental` flag, or `ZAPIER_EXPERIMENTAL` env var required. On the default MCP server the request/response trigger tools (`create-trigger-inbox`, `list-triggers`, the lease/ack/release tools, etc.) are now listed; the callback-driven `drainTriggerInbox` and `watchTriggerInbox` remain SDK/CLI-only. They stay available via the experimental subpath and `zapier-sdk-experimental` binary for backward compatibility. ### Patch Changes - Updated dependencies [d09592b] - @zapier/zapier-sdk@0.82.0 ## 0.17.1 ### Patch Changes - Updated dependencies [d96b5f6] - @zapier/zapier-sdk@0.81.1 ## 0.17.0 ### Minor Changes - 8d232d2: Deprecated `name` in favor of `key` for trigger inboxes. `name` continues to work as a deprecated alias. - `createTriggerInbox` now accepts an optional `key` parameter; `name` is deprecated. - `ensureTriggerInbox` now takes `key` as its required idempotency identifier; passing `name` still works but is deprecated. - `listTriggerInboxes` now accepts a `key` filter; the `name` filter is deprecated. - Trigger inbox locators (the `inbox` argument on `getTriggerInbox`, `updateTriggerInbox`, and related methods) now resolve non-UUID values by `key`. - Trigger inbox responses now include a `key` field alongside `name` (both hold the same value; `key` may be `null` when an inbox has no natural key). ### Patch Changes - Updated dependencies [8d232d2] - @zapier/zapier-sdk@0.81.0 ## 0.16.3 ### Patch Changes - Updated dependencies [072fe2b] - @zapier/zapier-sdk@0.80.2 ## 0.16.2 ### Patch Changes - Updated dependencies [4fd8dce] - @zapier/zapier-sdk@0.80.1 ## 0.16.1 ### Patch Changes - 5e2cf0d: The `extensions` option now also accepts new-style plugin descriptors. Existing callers are unaffected. - Updated dependencies [5e2cf0d] - @zapier/zapier-sdk@0.80.0 ## 0.16.0 ### Minor Changes - d67227b: Display trusted SDK deprecation notices from Zapier API responses. The SDK sniffs `zapier-sdk-deprecation-*` response headers (never on relay responses), warns once per notice id per process — with no opt-out — and emits an `api:deprecation_notice` event for wrappers. The CLI additionally renders notices as a boxed stderr warning after command output, and the MCP server attaches them to every tool result so agents relay the warning to users. ### Patch Changes - Updated dependencies [d67227b] - @zapier/zapier-sdk@0.79.0 ## 0.15.3 ### Patch Changes - b8ff1dd: Refactor the SDKs onto kitcore's new internal plugin model. kitcore (an internal building block) gained a new plugin model, and the SDKs were rebuilt on it behind a compatibility bridge, so existing behavior is unchanged. The only changes to the published packages' surface: - Removed the deprecated `sdk.addPlugin(...)` chain method (and the `WithAddPlugin` type / chain-style no-arg `createSdk()` doorway). Extend a built SDK with the top-level `addPlugin(sdk, plugin)` instead. - `@zapier/zapier-sdk` now re-exports the plugin-authoring helpers (`createSdk`, `defineMethod` / `definePlugin` / `declareMethod` / etc., `selectExports`, `addPlugin`). Note `createSdk` reuses the old doorway's name but now takes a root plugin, so a stale no-arg `createSdk()` call is a compile error rather than silent misbehavior. - Updated dependencies [b8ff1dd] - @zapier/zapier-sdk@0.78.0 ## 0.15.2 ### Patch Changes - Updated dependencies [365ad1b] - @zapier/zapier-sdk@0.77.2 ## 0.15.1 ### Patch Changes - Updated dependencies [3fa9190] - @zapier/zapier-sdk@0.77.1 ## 0.15.0 ### Minor Changes - 19303e0: `triggerWorkflow` (and `trigger-workflow`) now authenticates with Zapier credentials and runs the workflow as the authenticated account; triggering is limited to workflows that account can access. It now returns the trigger's `id`, `workflow_id`, and `created_at` on `data` (previously `{ workflow, status, body }`). The call is unchanged: pass the workflow id and optional `input`. ### Patch Changes - Updated dependencies [19303e0] - @zapier/zapier-sdk@0.77.0 ## 0.14.5 ### Patch Changes - Updated dependencies [27ca0c5] - @zapier/zapier-sdk@0.76.2 ## 0.14.4 ### Patch Changes - Updated dependencies [745e172] - @zapier/zapier-sdk@0.76.1 ## 0.14.3 ### Patch Changes - Updated dependencies [a7d2646] - @zapier/zapier-sdk@0.76.0 ## 0.14.2 ### Patch Changes - Updated dependencies [8e5253d] - @zapier/zapier-sdk@0.75.0 ## 0.14.1 ### Patch Changes - Updated dependencies [f56bfdb] - @zapier/zapier-sdk@0.74.1 ## 0.14.0 ### Minor Changes - 571f90d: Add zapier-sdk-package-operation header to identify the caller operation ### Patch Changes - Updated dependencies [571f90d] - @zapier/zapier-sdk@0.74.0 ## 0.13.37 ### Patch Changes - Updated dependencies [6c7627c] - @zapier/zapier-sdk@0.73.1 ## 0.13.36 ### Patch Changes - Updated dependencies [f963a9d] - @zapier/zapier-sdk@0.73.0 ## 0.13.35 ### Patch Changes - Updated dependencies [fcc758e] - @zapier/zapier-sdk@0.72.0 ## 0.13.34 ### Patch Changes - Updated dependencies [2521624] - @zapier/zapier-sdk@0.71.1 ## 0.13.33 ### Patch Changes - 3474ff3: Add `createConnection` and two lower-level building blocks for connecting an app from code, end to end: - `createConnection({ app, browser?, timeoutMs?, pollIntervalMs? })` — high-level: mints a connection URL, prints it (and opens it in a browser when it's safe to do so), waits for the user to finish, and returns the new connection. `browser` is `"auto"` (default — opens locally, skips CI / SSH / headless Linux), `"always"`, or `"never"`. The URL is always printed, so a skipped or failed open falls back to copy/paste. - `getConnectionStartUrl({ app })` — low-level: mints a short-lived, signed start URL bound to the current user/account. Returns `{ url, startedAt, expiresAt, app }`. - `waitForNewConnection({ app, startedAt, timeoutMs?, pollIntervalMs? })` — low-level: polls until a connection for the app created at or after `startedAt` appears, then returns `{ id, app, title? }`. Throws `ZapierTimeoutError` after `timeoutMs` (default 5 minutes). `createConnection` is the right call for most cases. Reach for the two low-level methods when you want to hand off the URL without blocking (call `getConnectionStartUrl` alone), or do something custom between minting the URL and waiting — email it, post it to Slack, render a QR code — then call `waitForNewConnection`. - Updated dependencies [3474ff3] - Updated dependencies [5ca445d] - @zapier/zapier-sdk@0.71.0 ## 0.13.32 ### Patch Changes - Updated dependencies [a790695] - @zapier/zapier-sdk@0.70.4 ## 0.13.31 ### Patch Changes - Updated dependencies [b83f0b6] - Updated dependencies [3fa4bbe] - @zapier/zapier-sdk@0.70.3 ## 0.13.30 ### Patch Changes - Updated dependencies [cafad12] - @zapier/zapier-sdk@0.70.2 ## 0.13.29 ### Patch Changes - Updated dependencies [eb30657] - @zapier/zapier-sdk@0.70.1 ## 0.13.28 ### Patch Changes - Updated dependencies [8f20472] - @zapier/zapier-sdk@0.70.0 ## 0.13.27 ### Patch Changes - Updated dependencies [c4df375] - @zapier/zapier-sdk@0.69.3 ## 0.13.26 ### Patch Changes - Updated dependencies [c50db26] - @zapier/zapier-sdk@0.69.2 ## 0.13.25 ### Patch Changes - Updated dependencies [da80c77] - @zapier/zapier-sdk@0.69.1 ## 0.13.24 ### Patch Changes - Updated dependencies [9f1e934] - @zapier/zapier-sdk@0.69.0 ## 0.13.23 ### Patch Changes - Updated dependencies [9d6bd4d] - @zapier/zapier-sdk@0.68.1 ## 0.13.22 ### Patch Changes - Updated dependencies [41a7c26] - @zapier/zapier-sdk@0.68.0 ## 0.13.21 ### Patch Changes - 9096184: Extract the plugin framework into a new sibling package `kitcore` that `@zapier/zapier-sdk` consumes as a workspace devDependency (bundled into the published dist, not a runtime dep). Existing SDK code is unaffected: `createZapierSdk`, `createSdk`, the `ZapierSdk` type, every SDK method, and the full `Zapier*` error hierarchy keep their names, codes, and `instanceof` semantics. Internally `createZapierSdk` now builds via the linear `createPluginStack().use(...).toSdk()` path, which substantially speeds up construction. One behavior change to note: `normalizeError` no longer wraps thrown `Error` subclasses, so a handler's `TypeError` or a userland `MyAppError` bubbles through unchanged and `instanceof` works again; only non-`Error` throws get wrapped. New stack-based composition surface for building on top of the SDK: `createZapierSdkStack(options)` (from the root and `/experimental`) returns the unsealed `PluginStack` that `createZapierSdk` materializes, and `createPluginStack`, `createCorePlugin`, and `addPlugin` are re-exported from the root. Build by chaining `.use(...)` and sealing with `.toSdk()`, or extend a sealed SDK in place with `addPlugin(sdk, plugin)`. The chain-style `createSdk().addPlugin(...)` pattern is deprecated (now logs a one-time warning) but still works; the CLI and MCP packages moved their internal assembly to stacks with no change to their commands or tools. - Updated dependencies [a950509] - Updated dependencies [9096184] - @zapier/zapier-sdk@0.67.0 ## 0.13.20 ### Patch Changes - 0eb6a76: Add the `triggerWorkflow` experimental code-substrate plugin. Lives behind `@zapier/zapier-sdk/experimental` only — the stable subpath does not surface it. Looks up the workflow's `trigger_url` via the durableworkflowzaps API, then POSTs the user-supplied JSON payload to that URL. The trigger endpoint is tokenized (the URL embeds a secret) and takes no auth header, so the SDK uses a raw `fetch` rather than the api plugin for the second leg. Custom fetch flows through `sdk.context.options.fetch` for tests. The workflow id is UUID-validated at the input boundary; trigger endpoint failures (non-2xx, or workflow with no published version) surface as descriptive errors. The CLI gets the `workflowIdResolver` picker for the workflow input. - Updated dependencies [66db7cb] - Updated dependencies [c7c8f64] - Updated dependencies [0eb6a76] - @zapier/zapier-sdk@0.66.0 ## 0.13.19 ### Patch Changes - 9138968: Add the workflow-run experimental code-substrate plugins: `listWorkflowRuns`, `getWorkflowRun`, and `getTriggerRun`. All three live behind `@zapier/zapier-sdk/experimental` only — the stable subpath does not surface them. `listWorkflowRuns` is paginated against the backend's cursor + limit contract; `getWorkflowRun` looks up a run by id; `getTriggerRun` walks from a trigger id to its associated run, useful immediately after firing a trigger when the caller has the trigger id but not yet the run id. All ID inputs are UUID-validated at the schema boundary. Handlers pass the API response through verbatim — schemas stay as `outputSchema` for docs and types, but consumers see any richer fields the server adds without an SDK release. Adds `workflowRunIdResolver` — a dependent resolver scoped to the parent workflow — so CLI commands taking a run id present an interactive picker via `sdk.listWorkflowRuns({ workflow })`. `getTriggerRun` does not register a picker for `trigger`; users typically have the trigger id from a recent fire and pass it directly. - Updated dependencies [9138968] - @zapier/zapier-sdk@0.65.0 ## 0.13.18 ### Patch Changes - 913aa6b: Add the workflow-version experimental code-substrate plugins: `publishWorkflowVersion`, `listWorkflowVersions`, and `getWorkflowVersion`. All three are registered only in `@zapier/zapier-sdk/experimental`; the stable subpath does not expose them. `listWorkflowVersions` is paginated (cursor + pageSize); `publishWorkflowVersion` POSTs `source_files` (filename → contents) plus optional `dependencies`, `zapier_durable_version`, and `enabled` (defaults to true) to publish a new version; `getWorkflowVersion` returns the full version state including source files. Handlers pass API responses through verbatim (no client-side `.parse()` re-emission) so callers see any richer fields the server adds later without an SDK release. Adds `workflowVersionIdResolver` — a dependent resolver scoped to a parent workflow, mirrored on `tableRecordIdResolver`'s shape — so commands that take a version id present an interactive picker via `sdk.listWorkflowVersions({ workflow })` in the CLI. All ID inputs are UUID-validated at the boundary so non-UUID strings fail with a clear schema error instead of an opaque 500 from the backend's `::uuid` cast. - Updated dependencies [913aa6b] - @zapier/zapier-sdk@0.64.0 ## 0.13.17 ### Patch Changes - dfa3cea: Add the durable-run-write experimental code-substrate plugins: `runDurable` and `cancelDurableRun`. Both are registered only in `@zapier/zapier-sdk/experimental`; the stable subpath does not expose them. `runDurable` POSTs to sdkdurableapi `/api/v0/runs` with `source_files` (filename → contents), optional `input`/`dependencies`/`zapier_durable_version`/`connections`/`app_versions`, and a `private` input that maps to `is_private` on the wire. Returns the run ID immediately in `initialized` status — callers that need terminal status poll via `getDurableRun`; no built-in polling. `cancelDurableRun` POSTs to `/api/v0/runs/:id/cancel`, returns `{ id, status: "cancelled" }` on success, and propagates `ZapierNotFoundError` (404) and `ZapierConflictError` (409 — run already terminal) so callers can distinguish those outcomes. `runDurable` passes the API response through verbatim (no client-side `.parse()` re-emission) so callers see any richer fields the server adds later without an SDK release. Input field naming follows the in-tree convention (`run` rather than `runId`); UUID-validated at the input boundary. `cancelDurableRun` reuses `durableRunIdResolver` from the reads MR for ID pickers. - Updated dependencies [dfa3cea] - @zapier/zapier-sdk@0.63.0 ## 0.13.16 ### Patch Changes - eb9b408: Add the durable-run-read experimental code-substrate plugins: `listDurableRuns` and `getDurableRun`. Both are registered only in `@zapier/zapier-sdk/experimental`; the stable subpath does not expose them. `listDurableRuns` is paginated (cursor + pageSize) per the sdkdurableapi `/api/v0/runs` contract; `getDurableRun` returns the full run state with nested execution and operations journal. Handlers pass API responses through verbatim (no client-side `.parse()` re-emission) so callers see any richer fields the server adds later without an SDK release. Also adds `durableRunIdResolver` in `src/resolvers/durableRunId.ts` so commands that take a run id present an interactive picker via `sdk.listDurableRuns()` in the CLI (uses `toIterable` to pull across pages). Input field naming follows the in-tree convention (`run` rather than the fork's `runId`); input is validated as a UUID at the boundary so non-UUID strings fail with a clear schema error instead of an opaque 500 from the backend's `::uuid` cast. - Updated dependencies [eb9b408] - @zapier/zapier-sdk@0.62.0 ## 0.13.15 ### Patch Changes - 4827ffe: Add the workflow-write experimental code-substrate plugins: `createWorkflow`, `updateWorkflow`, `enableWorkflow`, `disableWorkflow`, `deleteWorkflow`. All five are registered only in `@zapier/zapier-sdk/experimental`; the stable subpath does not expose them. The four ID-based ops (update, enable, disable, delete) reuse `workflowIdResolver` so callers get an interactive picker via `sdk.listWorkflows()`. `deleteWorkflow` is marked `confirm: "delete"` for an explicit confirmation prompt before the destructive call. Input field naming follows the in-tree convention (`workflow` rather than the fork's `workflowId`, matching `tableIdResolver`'s shape) and is validated as a UUID at the input boundary so non-UUID strings fail with a clear schema error instead of an opaque 500 from the backend's `::uuid` cast. Response shapes match what the durableworkflowzaps handlers actually emit — no fabricated `is_private` / `created_by_user_id` / `triggers` fields. Handlers pass API responses through verbatim (no client-side `.parse()` re-emission) so callers see any richer fields the server adds later without an SDK release. - Updated dependencies [104daa3] - Updated dependencies [4827ffe] - @zapier/zapier-sdk@0.61.0 ## 0.13.14 ### Patch Changes - f12598a: Add the workflow-read experimental plugins: `listWorkflows` and `getWorkflow`. Both are registered only in `@zapier/zapier-sdk/experimental`; the stable subpath does not expose them. `listWorkflows` uses `createPaginatedPluginMethod` (page-iterator + `pageSize`/`cursor`/`maxItems` options) so callers can iterate via `for await (const page of sdk.listWorkflows())` or `toIterable(sdk.listWorkflows())`. The backend does not paginate today; the SDK treats a missing `next_cursor` as the last page, so server-side pagination drops in without an SDK API change. Introduces `packages/zapier-sdk/src/plugins/codeSubstrate/shared.ts` with `codeSubstrateDefaults` (`{ categories: ["code-workflow"], experimental: true }`) that subsequent code-workflow plugins spread into their `createPluginMethod` configs. Also adds `workflowIdResolver` in `src/resolvers/workflowId.ts` (mirrors `tableIdResolver` / `triggerInboxResolver`) so commands that take a workflow id present an interactive picker via `sdk.listWorkflows()` in the CLI. Workflow-write commands (`createWorkflow`, `updateWorkflow`, `enable/disable/deleteWorkflow`) land in a follow-up MR. - Updated dependencies [f12598a] - @zapier/zapier-sdk@0.60.0 ## 0.13.13 ### Patch Changes - Updated dependencies [e9da7e9] - @zapier/zapier-sdk@0.59.0 ## 0.13.12 ### Patch Changes - Updated dependencies [afbd4b6] - @zapier/zapier-sdk@0.58.0 ## 0.13.11 ### Patch Changes - Updated dependencies [5457bdd] - @zapier/zapier-sdk@0.57.0 ## 0.13.10 ### Patch Changes - Updated dependencies [884d0fc] - @zapier/zapier-sdk@0.56.2 ## 0.13.9 ### Patch Changes - cc0c9cf: Clarified the `releaseOnError` option description for `drainTriggerInbox` and `consumeTriggerInbox`: errors release the message when the drain finishes, not immediately. - Updated dependencies [cc0c9cf] - @zapier/zapier-sdk@0.56.1 ## 0.13.8 ### Patch Changes - Updated dependencies [d2aa0e9] - @zapier/zapier-sdk@0.56.0 ## 0.13.7 ### Patch Changes - Updated dependencies [ce779d1] - @zapier/zapier-sdk@0.55.0 ## 0.13.6 ### Patch Changes - 22a1727: Add optional `name` parameter to `createTriggerInbox` method - Updated dependencies [22a1727] - @zapier/zapier-sdk@0.54.1 ## 0.13.5 ### Patch Changes - Updated dependencies [ecfb727] - @zapier/zapier-sdk@0.54.0 ## 0.13.4 ### Patch Changes - Updated dependencies [23352c8] - @zapier/zapier-sdk@0.53.0 ## 0.13.3 ### Patch Changes - Updated dependencies [7984fae] - @zapier/zapier-sdk@0.52.0 ## 0.13.2 ### Patch Changes - f5a734d: Updated the experimental Triggers notice in all three package READMEs to clarify that the feature is in closed beta, with a link to contact us for access. - Updated dependencies [ef1c97d] - Updated dependencies [f5a734d] - @zapier/zapier-sdk@0.51.0 ## 0.13.1 ### Patch Changes - cd8f37b: Collapse the approval-flow surface into a single tri-state `approvalMode` option. What changed: - `approvalMode` is now `"disabled" | "poll" | "throw"` (was `"poll" | "fail"`). - `"disabled"` is the default. While the approval flow is alpha, callers must opt in explicitly via `approvalMode: "poll"` or `approvalMode: "throw"` (or the `ZAPIER_APPROVAL_MODE` env var). On an approval-required response, `"disabled"` throws a `ZapierApprovalError` with `status: "approval_required"` without creating an approval. - The `isInteractive` SDK option and the `ZAPIER_IS_INTERACTIVE` env var have been removed. Their role is subsumed by `approvalMode`: choosing `"poll"` / `"throw"` is the explicit opt-in that previously required `isInteractive: true`. - `"fail"` has been renamed to `"throw"` (both the option value and the `ZAPIER_APPROVAL_MODE` env var value). The behavior is unchanged: throw a `ZapierApprovalError` carrying the approval URL so the caller can surface it. - `approvalMode`, `approvalTimeoutMs`, and `maxApprovalRetries` are now part of the public API (no longer marked `internal: true`). There is no back-compat shim. `approvalMode: "fail"` and `isInteractive: ` will fail Zod validation up front. - Updated dependencies [cd8f37b] - @zapier/zapier-sdk@0.50.0 ## 0.13.0 ### Minor Changes - 529663c: Add experimental support for triggers. ### Patch Changes - Updated dependencies [529663c] - @zapier/zapier-sdk@0.49.0 ## 0.12.1 ### Patch Changes - Updated dependencies [5ec7992] - @zapier/zapier-sdk@0.48.1 ## 0.12.0 ### Minor Changes - c7cff63: Adds an extension mechanism that lets the CLI and MCP server load additional plugin packages at runtime. Set `ZAPIER_SDK_EXTENSIONS` to a comma-separated list of package specifiers, or pass them via the new `extensions` option — methods they contribute show up automatically as CLI commands and MCP tools, no per-project wiring required. When a plugin tries to register a method, context field, or meta entry that's already registered by another plugin in the chain, `addPlugin` now logs a warning and skips the duplicate plugin's contribution rather than silently overwriting. This catches the common foot-gun of an extension accidentally shadowing a built-in SDK method. Intentional duplicates can be expressed via `composePlugins(...)`, and meta-only overrides (e.g. tagging a built-in method as deprecated) continue to work unchanged. ### Patch Changes - Updated dependencies [c7cff63] - @zapier/zapier-sdk@0.48.0 ## 0.11.9 ### Patch Changes - Updated dependencies [4ab820a] - @zapier/zapier-sdk@0.47.1 ## 0.11.8 ### Patch Changes - Updated dependencies [e45ce2f] - @zapier/zapier-sdk@0.47.0 ## 0.11.7 ### Patch Changes - Updated dependencies [fcb47ea] - @zapier/zapier-sdk@0.46.2 ## 0.11.6 ### Patch Changes - Updated dependencies [591ddb5] - @zapier/zapier-sdk@0.46.1 ## 0.11.5 ### Patch Changes - Updated dependencies [bd887ab] - @zapier/zapier-sdk@0.46.0 ## 0.11.4 ### Patch Changes - 783e180: Convert API query params from camelCase to snake_case (appKeys -> app_keys, pageSize -> page_size) to match the updated API contract. Also updated all `zapier-sdk-*` packages to Zod to 4.3.6 - Updated dependencies [783e180] - @zapier/zapier-sdk@0.45.2 ## 0.11.3 ### Patch Changes - cb0d898: Added telemetry headers so sdkapi can attribute traffic to the SDK entry point that produced it. Every outbound request now includes `x-zapier-sdk-version`, with `x-zapier-service` added when `ZAPIER_SDK_SERVICE` is set. Requests originating from `createZapierCliSdk` or `createZapierMcpServer` additionally include `x-zapier-sdk-package` and `x-zapier-sdk-package-version` identifying the wrapping package; direct `createZapierSdk` callers omit those two. Headers are applied after caller-supplied header merging, so they can't be spoofed via per-request `options.headers`. - Updated dependencies [cb0d898] - @zapier/zapier-sdk@0.45.1 ## 0.11.2 ### Patch Changes - Updated dependencies [15dce25] - @zapier/zapier-sdk@0.45.0 ## 0.11.1 ### Patch Changes - Updated dependencies [fd8660c] - @zapier/zapier-sdk@0.44.0 ## 0.11.0 ### Minor Changes - 8df8761: Add an experimental interactive approval flow for policy-gated actions. When an action requires approval, the SDK detects the `approval_required` response, prompts for approval in interactive sessions, and automatically retries the original request once approved. Non-interactive sessions receive a clear error explaining that approval is required. This flow is experimental and its behavior may change in future releases. ### Patch Changes - Updated dependencies [8df8761] - @zapier/zapier-sdk@0.43.0 ## 0.10.15 ### Patch Changes - Updated dependencies [707c57a] - @zapier/zapier-sdk@0.42.1 ## 0.10.14 ### Patch Changes - Updated dependencies [55e8330] - @zapier/zapier-sdk@0.42.0 ## 0.10.13 ### Patch Changes - Updated dependencies [3cf1a98] - @zapier/zapier-sdk@0.41.2 ## 0.10.12 ### Patch Changes - Updated dependencies [53c165a] - @zapier/zapier-sdk@0.41.1 ## 0.10.11 ### Patch Changes - Updated dependencies [912e960] - @zapier/zapier-sdk@0.41.0 ## 0.10.10 ### Patch Changes - Updated dependencies [e3f5a81] - @zapier/zapier-sdk@0.40.4 ## 0.10.9 ### Patch Changes - Updated dependencies [b250545] - @zapier/zapier-sdk@0.40.3 ## 0.10.8 ### Patch Changes - Updated dependencies [362bc56] - @zapier/zapier-sdk@0.40.2 ## 0.10.7 ### Patch Changes - Updated dependencies [5391c65] - @zapier/zapier-sdk@0.40.1 ## 0.10.6 ### Patch Changes - Updated dependencies [39e296a] - @zapier/zapier-sdk@0.40.0 ## 0.10.5 ### Patch Changes - Updated dependencies [b4c0560] - @zapier/zapier-sdk@0.39.1 ## 0.10.4 ### Patch Changes - Updated dependencies [a20d36a] - @zapier/zapier-sdk@0.39.0 ## 0.10.3 ### Patch Changes - Updated dependencies [2906101] - @zapier/zapier-sdk@0.38.0 ## 0.10.2 ### Patch Changes - Updated dependencies [307aa98] - @zapier/zapier-sdk@0.37.0 ## 0.10.1 ### Patch Changes - Updated dependencies [3a447d3] - @zapier/zapier-sdk@0.36.0 ## 0.10.0 ### Minor Changes - d4534f3: Add support for Tables. ### Patch Changes - Updated dependencies [d4534f3] - @zapier/zapier-sdk@0.35.0 ## 0.9.23 ### Patch Changes - 6c5bba9: Fix fetch type for app proxy without generated types. - Updated dependencies [6c5bba9] - @zapier/zapier-sdk@0.34.1 ## 0.9.22 ### Patch Changes - Updated dependencies [3700f6a] - @zapier/zapier-sdk@0.34.0 ## 0.9.21 ### Patch Changes - Updated dependencies [d9e0f1d] - @zapier/zapier-sdk@0.33.4 ## 0.9.20 ### Patch Changes - Updated dependencies [f676852] - @zapier/zapier-sdk@0.33.3 ## 0.9.19 ### Patch Changes - Updated dependencies [623dc25] - @zapier/zapier-sdk@0.33.2 ## 0.9.18 ### Patch Changes - 42edf6e: Remove test files from published packages - Updated dependencies [42edf6e] - @zapier/zapier-sdk@0.33.1 ## 0.9.17 ### Patch Changes - Updated dependencies [f442359] - @zapier/zapier-sdk@0.33.0 ## 0.9.16 ### Patch Changes - Updated dependencies [0feaeb1] - @zapier/zapier-sdk@0.32.5 ## 0.9.15 ### Patch Changes - Updated dependencies [1334eac] - @zapier/zapier-sdk@0.32.4 ## 0.9.14 ### Patch Changes - Updated dependencies [04000f6] - @zapier/zapier-sdk@0.32.3 ## 0.9.13 ### Patch Changes - Updated dependencies [a6dec83] - @zapier/zapier-sdk@0.32.2 ## 0.9.12 ### Patch Changes - Updated dependencies [c7be13e] - @zapier/zapier-sdk@0.32.1 ## 0.9.11 ### Patch Changes - Updated dependencies [250cb7d] - @zapier/zapier-sdk@0.32.0 ## 0.9.10 ### Patch Changes - Updated dependencies [026ae46] - @zapier/zapier-sdk@0.31.4 ## 0.9.9 ### Patch Changes - c98008a: Add callContext option to EventEmissionConfig to track where SDK method calls originate. MethodCalledEvent telemetry events now populate call_context with "sdk", "cli", or "mcp" instead of null. - Updated dependencies [c98008a] - @zapier/zapier-sdk@0.31.3 ## 0.9.8 ### Patch Changes - Updated dependencies [1ae0349] - @zapier/zapier-sdk@0.31.2 ## 0.9.7 ### Patch Changes - Updated dependencies [b0f273f] - @zapier/zapier-sdk@0.31.1 ## 0.9.6 ### Patch Changes - Updated dependencies [4a874c6] - @zapier/zapier-sdk@0.31.0 ## 0.9.5 ### Patch Changes - Updated dependencies [0055854] - @zapier/zapier-sdk@0.30.0 ## 0.9.4 ### Patch Changes - Updated dependencies [ad5ee3b] - @zapier/zapier-sdk@0.29.0 ## 0.9.3 ### Patch Changes - Updated dependencies [b2e5675] - @zapier/zapier-sdk@0.28.0 ## 0.9.2 ### Patch Changes - ffcd15a: Fix invalid JSON Schema output for z.any() and z.unknown() by emitting empty schema objects instead of description-only objects ## 0.9.1 ### Patch Changes - Updated dependencies [4ad0f34] - @zapier/zapier-sdk@0.27.1 ## 0.9.0 ### Minor Changes - 9fb0b48: Switch from "authentication" to "connection" everywhere. ### Patch Changes - Updated dependencies [9fb0b48] - @zapier/zapier-sdk@0.27.0 ## 0.8.5 ### Patch Changes - Updated dependencies [bfdd383] - @zapier/zapier-sdk@0.26.0 ## 0.8.4 ### Patch Changes - Updated dependencies [7ab8539] - @zapier/zapier-sdk@0.25.3 ## 0.8.3 ### Patch Changes - Updated dependencies [642713b] - @zapier/zapier-sdk@0.25.2 ## 0.8.2 ### Patch Changes - Updated dependencies [aacaf22] - @zapier/zapier-sdk@0.25.1 ## 0.8.1 ### Patch Changes - Updated dependencies [b0b7eb3] - @zapier/zapier-sdk@0.25.0 ## 0.8.0 ### Minor Changes - d72cda1: Deprecates request() in favor of self-contained fetch(). The fetch plugin now handles URL-to-relay transformation, header normalization, and body content-type inference directly instead of delegating to request. The request plugin is preserved as a backward-compatible shim that forwards to fetch. CLI and MCP now expose a fetch command via a new inputParameters registry concept for multi-positional-argument functions. ### Patch Changes - Updated dependencies [d72cda1] - @zapier/zapier-sdk@0.24.0 ## 0.7.6 ### Patch Changes - Updated dependencies [9664bd0] - @zapier/zapier-sdk@0.23.2 ## 0.7.5 ### Patch Changes - Updated dependencies [c95e1d4] - @zapier/zapier-sdk@0.23.1 ## 0.7.4 ### Patch Changes - Updated dependencies [7cf2b12] - @zapier/zapier-sdk@0.23.0 ## 0.7.3 ### Patch Changes - Updated dependencies [8ebde4b] - @zapier/zapier-sdk@0.22.1 ## 0.7.2 ### Patch Changes - Updated dependencies [f54f895] - @zapier/zapier-sdk@0.22.0 ## 0.7.1 ### Patch Changes - dd54c22: `request` and `fetch` now require auth and provide a more helpful error message - Updated dependencies [dd54c22] - @zapier/zapier-sdk@0.21.1 ## 0.7.0 ### Minor Changes - 7ad92fe: Remove standalone executable from zapier-sdk-mcp ## 0.6.0 ### Minor Changes - 33e2a8f: Added methods/commands for creating/listing/deleting client credentials. ### Patch Changes - Updated dependencies [33e2a8f] - @zapier/zapier-sdk@0.21.0 ## 0.5.1 ### Patch Changes - Updated dependencies [7bd3c5c] - @zapier/zapier-sdk@0.20.1 ## 0.5.0 - Update dependency to @zapier/zapier-sdk@0.20.0 after accidentally publishing a major version update. ## 0.4.15 ### Patch Changes - Updated dependencies [4dd27eb] - @zapier/zapier-sdk@1.1.0 ## 0.4.14 ### Patch Changes - Updated dependencies [e393401] - @zapier/zapier-sdk@1.0.3 ## 0.4.13 ### Patch Changes - Updated dependencies [00ef417] - @zapier/zapier-sdk@1.0.2 ## 0.4.12 ### Patch Changes - Updated dependencies [aba842a] - @zapier/zapier-sdk@1.0.1 ## 0.4.11 ### Patch Changes - Updated dependencies [97ff6c0] - @zapier/zapier-sdk@1.0.0 ## 0.4.10 ### Patch Changes - Updated dependencies [3bc3cad] - @zapier/zapier-sdk@0.18.4 ## 0.4.9 ### Patch Changes - Updated dependencies [7c59b01] - @zapier/zapier-sdk@0.18.3 ## 0.4.8 ### Patch Changes - Updated dependencies [76fb606] - @zapier/zapier-sdk@0.18.2 ## 0.4.7 ### Patch Changes - Updated dependencies [ee5beb6] - @zapier/zapier-sdk@0.18.1 ## 0.4.6 ### Patch Changes - Updated dependencies [c2eab85] - @zapier/zapier-sdk@0.18.0 ## 0.4.5 ### Patch Changes - Updated dependencies [79b47f7] - @zapier/zapier-sdk@0.17.0 ## 0.4.4 ### Patch Changes - Updated dependencies [870f2aa] - @zapier/zapier-sdk@0.16.3 ## 0.4.3 ### Patch Changes - f083442: Make zapier-sdk-mcp package public ## 0.4.2 ### Patch Changes - Updated dependencies [93cbb3c] - @zapier/zapier-sdk@0.16.2 ## 0.4.1 ### Patch Changes - Updated dependencies [142c1ce] - @zapier/zapier-sdk@0.16.1 ## 0.4.0 ### Minor Changes - 24ae4f0: Upgrade to Zod 4 - Update all packages to use Zod 4 - Migrate internal API access from `_def` to `_zod.def` - Update `z.record()` calls to include explicit key types - Fix schema introspection for documentation generation and CLI - Update MCP schema converter for Zod 4 structure ### Patch Changes - Updated dependencies [24ae4f0] - @zapier/zapier-sdk@0.16.0 ## 0.3.39 ### Patch Changes - d08fa90: Add proper license - Updated dependencies [d08fa90] - @zapier/zapier-sdk@0.15.13 ## 0.3.38 ### Patch Changes - Updated dependencies [9989512] - @zapier/zapier-sdk@0.15.12 ## 0.3.37 ### Patch Changes - b90e240: Fix MCP server graceful shutdown on SIGINT/SIGTERM ## 0.3.36 ### Patch Changes - Updated dependencies [64de0b0] - @zapier/zapier-sdk@0.15.11 ## 0.3.35 ### Patch Changes - ca83e51: Fix MCP server exiting immediately ## 0.3.34 ### Patch Changes - Updated dependencies [2f1fc5c] - @zapier/zapier-sdk@0.15.10 ## 0.3.33 ### Patch Changes - Updated dependencies [450b009] - @zapier/zapier-sdk@0.15.9 ## 0.3.32 ### Patch Changes - Updated dependencies [371315e] - @zapier/zapier-sdk@0.15.8 ## 0.3.31 ### Patch Changes - Updated dependencies [9f3695b] - @zapier/zapier-sdk@0.15.7 ## 0.3.30 ### Patch Changes - Updated dependencies [6a0e0db] - @zapier/zapier-sdk@0.15.6 ## 0.3.29 ### Patch Changes - Updated dependencies [712c02b] - @zapier/zapier-sdk@0.15.5 ## 0.3.28 ### Patch Changes - Updated dependencies [f7e552e] - @zapier/zapier-sdk@0.15.4 ## 0.3.27 ### Patch Changes - Updated dependencies [6657f05] - @zapier/zapier-sdk@0.15.3 ## 0.3.26 ### Patch Changes - Updated dependencies [e4a3457] - @zapier/zapier-sdk@0.15.2 ## 0.3.25 ### Patch Changes - 4c78fb0: Added `getInputFieldsSchema` plugin to retrieve JSON Schema for action inputs - Updated dependencies [4c78fb0] - @zapier/zapier-sdk@0.15.1 ## 0.3.24 ### Patch Changes - Updated dependencies [f92bc07] - @zapier/zapier-sdk@0.15.0 ## 0.3.23 ### Patch Changes - Updated dependencies [3f2f104] - @zapier/zapier-sdk@0.14.0 ## 0.3.22 ### Patch Changes - Updated dependencies [492e2f9] - @zapier/zapier-sdk@0.13.9 ## 0.3.21 ### Patch Changes - Updated dependencies [6de89a9] - @zapier/zapier-sdk@0.13.8 ## 0.3.20 ### Patch Changes - Updated dependencies [c1d3c9c] - Updated dependencies [16b4930] - @zapier/zapier-sdk@0.13.7 ## 0.3.19 ### Patch Changes - Updated dependencies [a563cda] - @zapier/zapier-sdk@0.13.6 ## 0.3.18 ### Patch Changes - Updated dependencies [05ce6f7] - @zapier/zapier-sdk@0.13.5 ## 0.3.17 ### Patch Changes - Updated dependencies [80732ea] - @zapier/zapier-sdk@0.13.4 ## 0.3.16 ### Patch Changes - Updated dependencies [53fa85e] - @zapier/zapier-sdk@0.13.3 ## 0.3.15 ### Patch Changes - Updated dependencies [325d5c2] - @zapier/zapier-sdk@0.13.2 ## 0.3.14 ### Patch Changes - Updated dependencies [a607e3a] - @zapier/zapier-sdk@0.13.1 ## 0.3.13 ### Patch Changes - Updated dependencies [53ad336] - @zapier/zapier-sdk@0.13.0 ## 0.3.12 ### Patch Changes - Updated dependencies [c2f88bc] - @zapier/zapier-sdk@0.12.1 ## 0.3.11 ### Patch Changes - Updated dependencies [21d8487] - @zapier/zapier-sdk@0.12.0 ## 0.3.10 ### Patch Changes - 407245e: Add packages to meta so we can document `fetch` for SDK but not CLI/MCP. - Updated dependencies [407245e] - @zapier/zapier-sdk@0.11.2 ## 0.3.9 ### Patch Changes - 0002fe9: Updated doc generation - Updated dependencies [0002fe9] - @zapier/zapier-sdk@0.11.1 ## 0.3.8 ### Patch Changes - Updated dependencies [12c6d3d] - @zapier/zapier-sdk@0.11.0 ## 0.3.7 ### Patch Changes - Updated dependencies [3184903] - @zapier/zapier-sdk@0.10.0 ## 0.3.6 ### Patch Changes - Updated dependencies [3cfed98] - @zapier/zapier-sdk@0.9.1 ## 0.3.5 ### Patch Changes - 5ccaec6: AST-based type gen instead of string-based. Added `add` function for locking app versions and generating types. Removed `lockVersion` and `generateTypes functions. Manifest matching on slug or implementation name. - Updated dependencies [5ccaec6] - @zapier/zapier-sdk@0.9.0 ## 0.3.4 ### Patch Changes - Updated dependencies [ed235b6] - @zapier/zapier-sdk@0.8.3 ## 0.3.3 ### Patch Changes - 2cf22f7: Fix broken table of contents in CLI and MCP READMEs ## 0.3.2 ### Patch Changes - Updated dependencies [bef5467] - @zapier/zapier-sdk@0.8.2 ## 0.3.1 ### Patch Changes - Updated dependencies [319a05f] - @zapier/zapier-sdk@0.8.1 ## 0.3.0 ### Minor Changes - 3a39eee: Add listInputFieldChoices method ### Patch Changes - Updated dependencies [3a39eee] - @zapier/zapier-sdk@0.8.0 ## 0.2.5 ### Patch Changes - Updated dependencies [096d674] - @zapier/zapier-sdk@0.7.0 ## 0.2.4 ### Patch Changes - 4315531: All CLI commands are now just local plugins used to build a CLI specific SDK, and that CLI specific SDK is used to generate the CLI docs. - Updated dependencies [4315531] - @zapier/zapier-sdk@0.6.4 ## 0.2.3 ### Patch Changes - Updated dependencies [5b74010] - @zapier/zapier-sdk@0.6.3 ## 0.2.2 ### Patch Changes - Updated dependencies [ac0624d] - @zapier/zapier-sdk@0.6.2 ## 0.2.1 ### Patch Changes - Updated dependencies [38fe5c4] - @zapier/zapier-sdk@0.6.1 ## 0.2.0 ### Minor Changes - c402bcd: Remove \_\_registry in favor of getRegistry that also provides categories for functions. ### Patch Changes - 8ef28ba: reducing any usage with minimal changes to runtime - Updated dependencies [c472d6f] - Updated dependencies [e08365e] - Updated dependencies [c402bcd] - @zapier/zapier-sdk@0.6.0 ## 0.1.4 ### Patch Changes - 218a3ca: reducing 'any' usage with minimal changes to runtime - Updated dependencies [218a3ca] - @zapier/zapier-sdk@0.5.2 ## 0.1.3 ### Patch Changes - c662f79: Add proper README with dynamically-listed methods - Updated dependencies [c662f79] - @zapier/zapier-sdk@0.5.1 ## 0.1.2 ### Patch Changes - Updated dependencies [741c385] - @zapier/zapier-sdk@0.5.0 ## 0.1.1 ### Patch Changes - 36a2825: Fix visibility of zapier-sdk-mcp package (make `restricted`)