Packages

@vercel/config

0.15.0 · 18 Nov 2026MIT628k / weekRepositoryHomepagenpmAtom feed

Upgrading @vercel/config From 0.0.28 to 0.15.0

39 releases in betweennotes for 37

Reading releases, release notes and advisories…

  1. 0.0.28yours
  2. 12 releases
  3. 0.1.0major
  4. 1 release
  5. 0.2.0major
  6. 1 release
  7. 0.3.0major
  8. 0.4.0major
  9. 0.5.0major
  10. 6 releases
  11. 0.6.0major
  12. 1 release
  13. 0.7.0major
  14. 2 releases
  15. 0.8.0major
  16. 0.9.0major
  17. 0.10.0major
  18. 0.11.0major
  19. 0.12.0major
  20. 0.13.0major
  21. 0.14.0major
  22. 1 release
  23. 0.15.0target
  24. 1 pre
3+
changes to make
0
advisories fixed
23+
new
5+
fixes

Counted from 37 of 39 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • Breaking0.14.0
  • Breaking0.11.0
  • Deprecated0.13.0

Release by release

  1. 0.14.1 – 0.15.02 releases, no release note

  2. 0.14.0

    Migration needed27 Oct 2026
    • Breaking

      Remove the deprecated array format for schedules. schedules in vercel.json, in Build Output config.json, and from getDevManifest must be an object keyed by schedule name. @vercel/config no longer exports Schedule (use ScheduleDefinition), and @vercel/client no longer exports VercelConfigSchedule.

  3. 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.

  4. 0.12.0

    8 Oct 20261 new
    • New

      Add an optional service to function-target schedules, naming the service that owns function. function is then the path within that service. vercel dev does not run service-hosted schedule targets yet.

  5. 0.11.0

    Migration needed6 Oct 2026
    • Breaking

      Breaking (beta): the nested expression/target schedules format is no longer supported in vercel.json or Build Output. schedules entries use schedule plus exactly one of path, function, topic, or entrypoint, with optional name, timezone, and jitter. When name is omitted, it defaults to a hash of the target and cron expression, matching the name the API derives. vercel build leaves unnamed schedules unnamed in config.json, except entrypoint schedules, which keep the derived name their function dispatches on.

  6. 0.10.0

    5 Oct 20261 new
    • New

      Flat path schedules accept an optional requestMethod of GET or POST, defaulting to POST. vercel build writes it to Build Output, and vercel dev invokes path schedules with it.

  7. 0.9.0

    2 Oct 20261 new
    • New

      Make name optional for flat schedules entries. When omitted, the name defaults to a hash of the target and cron expression, matching the name the API derives. vercel build leaves unnamed schedules unnamed in config.json, except entrypoint schedules, which keep the derived name their function dispatches on.

  8. 0.8.0

    2 Oct 20262 new
    • New

      Accept the flat schedules format (schedule plus one of path, function, topic, or entrypoint) in VercelConfig, and export FlatScheduleDefinition, LegacyScheduleDefinition, and ScheduleDefinition types. The nested expression/target format is still accepted.

    • New

      Add the optional skipMiddlewareRequestBody boolean to VercelConfig, matching the vercel.json schema. When enabled, routing middleware omits the request body while the destination request body is preserved. Defaults to false.

13 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.