Packages

@vercel/build-utils

15.5.0 · 18 Nov 2026Apache-2.07.9M / weekRepositoryHomepagenpmAtom feed

Upgrading @vercel/build-utils From 13.36.3 to 15.5.0

53 releases in betweennotes for 45

Reading releases, release notes and advisories…

  1. 13.36.3yours
  2. 21 releases
  3. 14.10.2breaking
  4. 10 releases
  5. 14.19.0breaking
  6. 8 releases
  7. 15.0.0major
  8. 2 releases
  9. 15.1.0breaking
  10. 7 releases
  11. 15.5.0target
  12. 15 pre
6+
changes to make
0
advisories fixed
32+
new
26+
fixes

Counted from 45 of 53 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • Breaking15.1.0
  • Breaking15.0.0
  • Breaking14.19.0
  • Breaking14.10.2
  • Deprecated14.23.0
  • Deprecated14.21.0

Release by release

  1. 15.1.1 – 15.5.08 releases, no release note

  2. 15.1.0

    Migration needed27 Oct 20261 new
    • 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.

    • New

      Add an experimental Buildah image store cache, enabled with VERCEL_BUILDAH_STORE_CACHE=1, so builds reuse images and layers from earlier deployments. Concurrent service builds share one --source-date-epoch per deployment so their layers stay reusable. @vercel/build-utils now exports resolveBuildConcurrency().

  3. 15.0.2

    23 Oct 20261 fix
    • Fixed

      Report the runtime preset for services without a framework.

  4. 15.0.1

    22 Oct 20261 new
    • New

      Support livenessProbe in vercel.json#daemons.

  5. 15.0.0

    Migration needed22 Oct 20261 new · 1 fix
    • Breaking

      Remove the legacy BYOC extension's build-output collection and deserialization utilities, Lambda finalization and size validation, and serverless environment/streaming helpers. BYOC function preparation now uses vercel deploy describe.

    • New

      Allow explicitly selecting Node.js 26 for local builds without an environment variable.

    • Fixed

      Accept a command argument array and root with Dockerfile and Containerfile schedule entrypoints. This adds configuration support; building and executing these schedules will follow separately.

  6. 14.23.0

    Deprecation20 Oct 20261 new · 2 fixes
    • 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.

    • Fixed

      Accept service bindings on daemons in vercel.json.

    • Fixed

      Fix ENOENT build failures when daemons are deployed alongside a zero-config server app that has no public/ directory.

  7. 14.22.0

    19 Oct 20261 new · 1 fix
    • New

      Add functions[glob].installCommand. For matching @vercel/node functions, an empty string skips the dependency install and a non-empty value runs instead of the default install. Builds warn when the property matches functions of other runtimes, which ignore it.

    • Fixed

      Use Vercel Flags project activation metadata to detect when to embed flag definitions, including builds without installed SDK packages. Preserve explicit embedding overrides and existing SDK detection for projects without activation metadata.

  8. 14.21.3

    16 Oct 20261 fix
    • Fixed

      Display the edge middleware deprecation warning in yellow with a bold WARNING! prefix during builds and at vercel dev startup. Add an optional builder hook for detecting startup warnings without starting a development server.

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