[PDE-4089] chore(cli, core, schema): Release v16.0.0 #929
+12,373
−8,424
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[email protected]
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):
cli
oclif
suite of packages have been upgraded to support the latestoclif
major version (v4) (#890).core
❗ Node.js v16.x is no longer supported (#890)
❗ 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.❗ Due to changes in the underlying
dotenv
library (see changelog) (#926), when usingzapier.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 toSECRET_HASH="something-with-a-#-hash"
SECRET_BACKTICK=something-with-a-`-backtick
: change it toSECRET_BACKTICK="something-with-a-`-backtick"
skipEncodingChars
property typing for z.request object (#928)schema
schema-to-ts
schema-to-ts
package is now part of the repository root "yarn workspaces" (#913)misc
@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/[email protected]
@oclif/[email protected]
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.1