Packages

@vercel/build-utils

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

Upgrading @vercel/build-utils From 14.23.0 to 15.5.0

12 releases in betweennotes for 4

Reading releases, release notes and advisories…

  1. 14.23.0yours
  2. 15.0.0major
  3. 2 releases
  4. 15.1.0breaking
  5. 7 releases
  6. 15.5.0target
  7. 15 pre
2+
changes to make
0
advisories fixed
3+
new
2+
fixes

Counted from 4 of 12 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

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.

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.