Releases: heroku/heroku-buildpack-nodejs
Releases · heroku/heroku-buildpack-nodejs
Release list
v358
- Added Node.js 26.5.0 (linux-amd64)
- Fixed
npm installfailing on npm 12, which removed the--unsafe-permflag the buildpack was passing. (#1704) - Relocated the npm binary installation (
npm@<version>bootstrap) intolib/package_managers/npm.shas part of the error-handling migration. This is a behavior-neutral move; the build errors and their messages are unchanged. (#1701) - Improved the Node.js version-resolution build errors, and added error handling for previously-unclassified resolver failures. (#1698)
v357
- Migrated Node.js version-resolution build errors (unresolvable version, invalid semver requirement) onto the call-site failure-classification framework. The error messages are unchanged. (#1687)
- Migrated Node.js download and checksum-validation build errors onto the failure-classification framework, and removed the obsolete AWS proxy (
NO_PROXY=amazonaws.com) build warning, which dated to when Node.js binaries were served from an S3 mirror. (#1688)
v356
- Added Node.js 26.4.0 (linux-amd64)
- Added clearer
npm installbuild errors for npm 12's new install-blocking defaults: blocked install scripts (ESTRICTALLOWSCRIPTS), git dependencies (EALLOWGIT), and remote-URL dependencies (EALLOWREMOTE), with guidance on approving scripts or adjusting.npmrc. (#1683)
v355
- Added Node.js 24.18.0 (linux-amd64)
- Added Node.js 22.23.1 (linux-amd64)
v354
- Added Node.js 26.3.1 (linux-amd64)
- Added Node.js 24.17.0 (linux-amd64)
- Added Node.js 22.23.0 (linux-amd64)
- Removed the
Build succeeded!log line from the build output. In multi-buildpack builds this misleadingly implied the entire build had succeeded when only the Node.js buildpack had finished. (#1672) - Improved the multiple-lockfiles build error message: it now inlines actionable, per-package-manager fix steps (covering npm, Yarn, and pnpm) instead of linking out to a knowledge base article. (#1673)
v353
- Fixed pnpm 11 apps experiencing
ERR_PNPM_ABORTED_REMOVE_MODULES_DIR_NO_TTYerrors at runtime when pnpm commands are executed. (#1667)
v352
- Deprecated Node.js 25.x (reached end-of-life). (#1665)
v351
- Added Node.js 26.3.0 (linux-amd64)
- Tolerate
ENOENTfrompnpm store prunewhen the pnpm store has no fetched package files, fixing build failures on pnpm <9.12.0 for projects that resolve with no external dependencies. (#1654)