shipfeedAI news, curated daily

00:38:18 CET
21 MAY00:38:18shipfeed
pull to refreshlast sync
Just in — 30 new
§ feed · storyline

Legacy build image is being deprecated on September 1, 2025

Vercel deprecates its legacy build image and Node.js 18 support on September 1, 2025, after which new builds on the legacy image will fail; minimum supported Node.js version moves to 20.x.

Apr 10 · · primary fetch1 sourceupdated Apr 10 ·

Node.js 18 (LTS support ends April 30, 2025) and the Vercel legacy build image will be deprecated on September 1, 2025. If you are still using the legacy build image on this date, new builds will display an error. What changes between the legacy build image and latest build image? How do I know if I am still using the legacy build image? Will my existing deployments be affected? Existing deployments However, the Node.js version will need to be updated on your next deployment.will not be affected. How can I see if my projects are affected? You can see which projects are affected by this deprecation by running the following commands: How do I upgrade? To upgrade with the dashboard, and upgrade the version.visit the Build and Deployment settings for your project To upgrade with code, use the field in :enginespackage.json This date coincides with the on the Vercel platform.

Learn more about .previously announced deprecation of Node.js 18differences between build images Read more The minimum version of Node.js is now 20.x The Python toolchain version is now 3.12 The Ruby toolchain version is now 3.3.x Projects using Node.js 18.x in use the legacy build imageBuild and Deployment…

read full article on vercel.com
§ sources1 publication · timeline below
  1. vercel.comLegacy build image is being deprecated on September 1, 2025primary