Following the Node.js 18 end of life on April 30, 2025, Vercel is deprecating Node.js 18 for Builds and Functions on September 1, 2025.
Existing deployments with Serverless Functions will not be affected, but new deployments will require a Node.js version upgrade.
More details and upgrade steps are shared in the changelog:
Will new commits pushed to existing deployments update the deployments?
Hi @atreya-4341, welcome to the Vercel Community!
New deployments will require a Node.js version upgrade.
Thank you for the confirmation.
What about new commits to deployments created before September 1st
Let’s say I already have a deployment running that was deployed today. And maybe I push a new commit on September 2nd to a branch that updates the deployment created today.
Will the deployment reflect the changes in the new commit made on September 2nd for a deployment that was created today using an old version of Node.js such 18.
If you need clarification please let me know.
New commits create new deployments, so you will not be able to update an existing deployment. You will be able to deploy new commits on your existing projects if they are updated to use Node.js 20 or 22.
As of April 30, 2025, the Node.js project no longer provides security updates, bug fixes, or maintenance for version 18. Please update your project to use a more recent version to help keep your site safe and secure 
Ok yes, that makes perfect sense. It is as I feared…
Thank you very much for the clarification!
Hi, this is an unusual question but I would greatly appreciate any help you can provide.
We have an existing running project deployed with Node.js 18 setting made by a previous developer who unfortunately died suddenly due to a heart attack before he could do a proper turnover of the project.
We are still in the process of developing a new system from scratch to replace the existing one that is currently in use because aside from the hosting account, unfortunately no documentation was left by the programmer to maintain the project.
The package.json indicates the code uses Angular, no engine node setting was specified.
Question 1) If no commits / changes to the project are scheduled this year, can we delay upgrading the node version of the current running project that uses firebase as its nosql database? That is, would the project still relatively run without the node.js version change? In asking this we are accepting the security risk involved. It is only that we are pressed for time in developing a new system given the untimely passing of the previous developer.
Question 2) If we have to change the node version, do i need to do a complete new deployment process or is there a more efficient / easier way to apply the new node version change without risking the integrity of the existing deployment? Asking because there was no documentation provided by the original developer and aside from this Vercel account, we do not have access to the repository where the project is saved.
I will be grateful for any assistance and insights you may have. Thank you.
Sorry to hear about your developer’s passing.
Existing deployments will continue to work. Only new deployments are affected on September 1, 2025. So your current project should still run as it is until you deploy new changes to production.
When you’re ready to change the Node.js version, a new deployment is needed. You can do that by updating the Node.js version in project settings and then pushing code to a connected Git repository or using the CLI.
I hope that helps!
Hi @amyegan , thank you so much for your very helpful response.
I apologize for being late in mine. I am very grateful for your clarification on the changes.
Cheers!