Released: 2026-10-30
This release adds a --fail-for-publishing flag to zapier-platform validate, so a CI check can fail while your integration still has publishing tasks. It also redacts secret-looking query params from URLs in error messages, fixes duplicated query params in requests built from a rendered auth template, and makes generated TypeScript projects work with any package manager.
It also adds experimental domain-filter commands. They are hidden from help while they are in development and may change, so do not rely on them yet.
Without the flag, validate exits with a non-zero code only when your integration is structurally invalid. With it, validate also exits with code 1 when the server-side checks report publishing tasks. A passing run does not guarantee that zapier-platform promote succeeds, because promote runs more checks. See the validate command reference.
- [feature] Add a
--fail-for-publishing flag to validate that exits with a non-zero code when publishing tasks remain (#1362)
- [feature] Add experimental
domain-filter:get, domain-filter:set, and domain-filter:unset commands, hidden from help (#1351)
- [fix] Set
engines.node to >=22 to match the Node.js version the CLI already requires at runtime, so npm warns at install time (#1360)
- [fix] Generated TypeScript projects no longer hardcode
npm in their scripts, so they work with pnpm, Yarn, and Bun (#1363)
- [fix] Redact secret-looking query params, such as
api_key or token, from URLs in thrown error messages, stack traces, and logs (#1368)
- [fix] Rendered auth templates no longer repeat query params that match the target request, which duplicated them in proxied requests (#1365)
None!
- [chore] Pin
simple-git to 3.36.0 (CVE-2026-28292, CVE-2026-6951) and bump tmp, @xmldom/xmldom, form-data, adm-zip, and vitest (#1355)
- [chore] Speed up and stabilize the Windows CLI test job (#1356)
- [chore] Replace the unmaintained
mock-fs test dependency with real temporary directories, ahead of Node.js 26 (#1367)
Last modified on October 30, 2026
