Packages

@vercel/build-utils

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

Upgrading @vercel/build-utils From 13.2.10 to 13.2.11

1 release in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 13.2.10Newest 13.x13.36.3Latest15.5.0
  1. 13.2.10yours
  2. 13.2.11target

Before you upgrade

Tick each one off as you go
  • Breaking13.2.11
  • Breaking13.2.11
  • Breaking13.2.11
  • Breaking13.2.11
  • Breaking13.2.11
  • Breaking13.2.11
  • Breaking13.2.11
  • Breaking13.2.11
  • Breaking13.2.11
  • Breaking13.2.11

Release by release

  1. 13.2.11

    Migration needed16 Jan 202658 new · 71 fixes
    • Breaking

      Remove getSpawnOptions

    • Breaking

      Remove env var check for node24

    • Breaking

      Remove --unsafe-perm from npm install command

    • Breaking

      Drop Node.js 18, bump minimum to Node.js 20

10 other lines we could not sort, mostly version bumps
  • Revert "Remove getSpawnOptions"

    13.2.11
  • Revert "[build-utils] Fix corepack packageManager detection on monorepos"

    13.2.11
  • Revert "Revert "Revert "Fix corepack packageManager detection on monorepos"""

    13.2.11
  • Revert "Revert "Fix corepack packageManager detection on monorepos""

    13.2.11
  • Revert "Revert "warn on mismatched corepack and detected package managers""

    13.2.11
  • Revert "warn on mismatched corepack and detected package managers"

    13.2.11
  • Revert "Fix corepack packageManager detection on monorepos"

    13.2.11
  • Revert "Revert "Default ruby to only currently supported version (3.2.0)""

    13.2.11
  • Revert "Default ruby to only currently supported version (3.2.0)"

    13.2.11
  • Revert "[build-utils] Allow file-ref sema to be controlled through env flag"

    13.2.11

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.