@zeit/schemas
2.38.0 · 10 Jan 2025MIT5.1M / weekRepositoryHomepagenpmAtom feed
Upgrading @zeit/schemas From 1.0.1 to 1.7.0
14 releases in betweenevery note read
Reading releases, release notes and advisories…
Release by release
- New
Blacklist all
NOW_*env vars for deployments - Fixed
Adjust max concurrent reqs per slot
- New
- New
Add
slotkey forcloud: v2
- New
- Fixed
Allow EnvKeys for
config.build: 540869f76919f88111b869346ce77c6aa1607171
- Fixed
- New
Add
deployment.envvalidation: eae1cf85511ad044d1b0aa6a8cd81b17859f2554 - New
Add the
EnvKeyblacklist: dfc9535204fbf9aaed9d5a114fb8daa4529c94ca - New
Add env value too long test case: 1123ae5e05d0ef06a4c5d5fe01dbe62c7083ed1a
- New
- New
Add deployment
build.envschema
- New
- Fixed
We need to check the env field's string check first.
- Fixed
- New
Validate env types
- New
- New
Added
limitsto deployment config schema
- New
2 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.