Packages

@vercel/build-utils

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

Upgrading @vercel/build-utils From 14.1.1 to 14.23.0

34 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 14.1.1Latest15.5.0
  1. 14.1.1yours
  2. 14 releases
  3. 14.10.2breaking
  4. 10 releases
  5. 14.19.0breaking
  6. 7 releases
  7. 14.23.0target

Before you upgrade

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

Release by release

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

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

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

  4. 14.21.2

    15 Oct 20261 new
    • New

      Add opt-in support for Node.js 26.

  5. 14.21.1

    14 Oct 20261 fix
    • Fixed

      Detect Yarn 4 from lockfile versions 9 and 10 (written by Yarn 4.14+), so workspace-scoped installs and the Yarn 3/4 enableGlobalCache setup apply to newer Yarn 4 projects.

  6. 14.21.0

    Deprecation13 Oct 20261 new
    • Deprecated

      Accept instances for daemons in vercel.json. replicas is deprecated and ignored when instances is set. Daemon build output now writes instances.

    • New

      Support terminationGracePeriodSeconds in vercel.json#daemons.

  7. 14.20.1

    9 Oct 20261 fix
    • Fixed

      Parse yarn.lock with js-yaml safeLoad so custom JS tags like !!js/function are rejected

  8. 14.20.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.

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.