❗ Node.js 22 Support
Zapier Platform v18 runs on Node.js 22 runtime. This is a breaking change as it may affect compatibility with older Node.js versions and dependencies.❗ Schema Changes
TheskipCleanArrayInputData experimental flag has been replaced with cleanInputData. This provides more consistent data cleaning behavior across the platform. This change is breaking only if you’re using skipCleanArrayInputData.
See cleanInputData flag documentation for more details on how to configure this behavior.
❗ New Throttling Middleware
A newthrowForThrottling middleware has been added to prevent afterResponse middleware from suppressing 429 (throttling) responses. This ensures proper handling of rate limiting scenarios. This change is breaking if you want to handle 429 responses in your afterResponse. See v18.x and above: the built-in throwForThrottling middleware for how to handle 429s yourself.
New Executable Name zapier-platform
The CLI now includes a new executable name zapier-platform while deprecating the old zapier command. Both will work for now, but zapier-platform is the recommended command going forward.
Apart from these major changes, here are the detailed release notes for this release (note that ❗ denotes a breaking change):
cli
- 🎉 Add executable name
zapier-platformand deprecatezapier(#1181) - 🔨 Update outdated dependencies with security vulnerabilities (#1111)
- 🔨 Apply prettier formatting to generated auth files since gen.fs.write bypasses transform streams
- 🔨 Add ESM wrapper improvements for better module support
core
- ❗ Add Node.js 22 support (#1078)
- 🎉 Add
throwForThrottlingmiddleware with backward-compatible default behavior (#1151) - 🐛 Add better error message for 413 responses (#1110)
schema
- ❗ Replace
skipCleanArrayInputDatawithcleanInputData(#1183) - 🔨 Add global
cleanInputDataflag for consistent data cleaning behavior
misc
- ❗ Major dependency updates across all packages (#1079)
- 🔨 Update CI configuration for Node.js 22 support
- 🔨 Pin exact xmldom version for security