zapier-platform-cli
Advanced tools
Changelog
16.0.0
released 2024-12-16
Version 16.0.0
is a breaking change release that contains some important housekeeping updates that put us in a better spot to support some exciting changes coming up in future versions. Here is a quick breakdown of the two main breaking changes:
1. The minimum supported version of Node.js is now v18.18. We’ve officially dropped support for Node.js v16.x, which has been designated end-of-life since September 2023.
2. Integrations using zapier-platform-core@16.0.0
and onwards will default to running on the ARM architecture in AWS Lambda. Note: If you believe your integrations have run into runtime incompatibilities due to this change, please reach out to our support team and we may be able to opt your integration out of running on ARM.
Here are the detailed release notes for this release (note that ❗ denotes a breaking change):
oclif
suite of packages have been upgraded to support the latest oclif
major version (v4) (#890).:exclamation: Node.js v16.x is no longer supported (#890)
:exclamation: Integrations running on zapier-platform-core
v16 and onwards will run on the ARM architecture by default. This means means they will run on AWS Graviton2 processors (previously, the AWS Lambda runtime was based on x86 architecture). For more details on what this means on a technical level, please check out: AWS Lambda on Graviton 2.
:exclamation: Due to changes in the underlying dotenv
library (see changelog) (#926), when using zapier.tools.env.inject()
, we always recommend "double quoting" your environment variable values. Please make sure to consider if the following cases would apply to your .env
files:
SECRET_HASH=something-with-a-#-hash
: change it to SECRET_HASH="something-with-a-#-hash"
SECRET_BACKTICK=something-with-a-`-backtick
: change it to SECRET_BACKTICK="something-with-a-`-backtick"
skipEncodingChars
property typing for z.request object (#928)schema-to-ts
package is now part of the repository root "yarn workspaces" (#913)@eslint/eslintrc@^3.2.0
@eslint/js@^9.16.0
globals@^15.13.0
eslint-plugin-standard
lerna
from 6.4.1 to 8.0.2husky
from 7.0.4 to 9.1.7mocha
from 10.8.2 to 11.0.1eslint
from 8.32.0 to 9.16.0eslint-plugin-import
from 2.27.5 to 2.31.0eslint-plugin-mocha
from 9.0.0 to 10.5.0eslint-plugin-n
from 15.6.1 to 17.14.0eslint-plugin-promise
from 6.1.1 to 7.2.1prettier
from 2.8.3 to 3.4.1oclif@^4.15.1
@oclif/core@4.0.28
@oclif/plugin-version@2.2.15
stdout-stderr
oclif/dev-cli
@oclif/command
@oclif/config
archiver
5.3.1 to 7.0.1gulp-prettier
from 4.0.0 to 5.0.0marked
4.2.12 to 14.1.4marked-terminal
from 5.2.0 to 7.2.1read
from 2.1.0 to 4.0.0fs-extra
from 11.1.1 to 11.2.0yeoman-environment
from 3.3.0 to 3.19.3semver
from 7.5.2 to 7.6.3node-fetch
from 2.6.7 to 2.7.0adm-zip
from 0.5.10 to 0.5.16browserify
from 17.0.0 to 17.0.1cli-table3
from 0.6.3 to 0.6.5tmp
from 0.2.1 to 0.2.3traverse
from 0.6.7 to 0.6.10dotenv
from 12.0.4 to 16.4.5semver
from 7.5.2 to 7.6.3node-fetch
from 2.6.7 to 2.7.0form-data
from 4.0.0 to 4.0.1prettier
from 3.2.5 to 3.4.1Changelog
15.19.0
released 2024-11-25
For optimal performance, an optional argument has been added to z.dehydrate to allow devs to control the cache duration on hydrators. The default cache duration for hydrators is unchanged (5 minutes).
Also, with the new optional meta
field object added to the FieldSchema object, devs now have a supported mechanism for storing field-specific context which may be obtained when constructing dynamic needs, and then making that context available during actual action execution in the perform method.
Lastly, the zapier scaffold now supports TypeScript (TS) applications. It automatically detects TS and JS projects if the --entry
flag isn't provided, so that it can generate and edit the right files in the right places, given TS projects tend to keep their files in ./src.
zapier scaffold
command (#884)timezone
and withSearch
fields to the bundle.meta
object (#922)BeforeRequestMiddleware
typings to require url
in the request object (#924)meta
field support for the FieldSchema
(#883)None!
Changelog
15.18.1
released 2024-11-01
zapier invoke --debug
doesn't print HTTP logs for requests that aren't sent by z.request()
(#907)None!
Changelog
15.18.0
released 2024-10-24
init
output (#894)nx
argument to z.cache.set()
(#900)process.exit(1)
on catching an EMFILE
error inside checkMemory()
(#901)None!
z.request
responses and deprecate .json
(#895)Changelog
15.17.0
released 2024-10-11
Introducing three major updates, with the first two aimed at improving your development experience:
zapier invoke
command: This powerful new command enables you to emulate Zapier's production environment locally. Test triggers, actions, and authentication flows right from your terminal without deploying to Zapier. This is especially valuable for debugging, development, and quick testing iterations. Learn more about the command in the README or by typing zapier invoke --help
in your terminal.zapier-platform-cli
's CI testing, it still works on Node.js 16, except for the zapier invoke auth start
command. But using Node.js 18 or later is recommended, as we'll be dropping support for Node.js 16 in an upcoming major release.As usual, all other improvements and bug fixes are listed below.
zapier invoke
command (#856, #872, #878)zapier convert
command not writing bulkReads
to separate files (#881)ResponseError
type (#877)None!
Changelog
15.15.0
released 2024-09-18
This release introduces "Buffered Create Actions", currently only available for internal use. A Buffered Create allows you to create objects in bulk with a single or fewer API request(s). This is useful when you want to reduce the number of requests made to your server. When enabled, Zapier holds the data until the buffer reaches a size limit or a certain time has passed, then sends the buffered data using the performBuffer
function you define.
None!
performBuffer
and buffer
to operation
schema to support Buffered Create Actions (#832)