Packages

@vercel/config

0.15.0 · 18 Nov 2026MIT628k / weekRepositoryHomepagenpmAtom feed

Upgrading @vercel/config From 0.12.0 to 0.13.0

1 release in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 0.12.0Newest 0.x, Latest0.15.0
  1. 0.12.0yours
  2. 0.13.0target
1
change to make
0
advisories fixed
1
new
0
fixes

Before you upgrade

Tick each one off as you go
  • Deprecated0.13.0

Release by release

  1. 0.13.0

    Deprecation20 Oct 20261 new
    • Deprecated

      schedules in vercel.json can now be an object keyed by schedule name, like "schedules": { "nightly": { "schedule": "0 0 * * *", "path": "/api/cron" } }. vercel build writes schedules to Build Output config.json in the format it was given, and builders can return it from getDevManifest. The array of named schedules still works but is deprecated, and vercel build and vercel dev warn when it's used.

    • New

      Require name for schedules entries in vercel.json and Build Output config.json. Schedules without a name no longer get a derived default name, and getScheduleName and defaultScheduleName are removed from @vercel/build-utils.

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.