Nodejs.org ends support for Node.js version 20 on April 30, 2026. Consequently, Acquia ends support for Node.js version 20 on Wednesday, April 15, 2026. At that time, Acquia removes Node.js version 20, and upgrades all remaining environments to Node.js version 22. This deadline is final because applications must upgrade to ensure continued security.
Acquia recommends that customers move to Node.js version 22 after appropriate testing. For applications that use Front End Hosting - Advanced, Node.js versions 22 and 24 are available.
Note
Acquia schedules managed upgrades for any application that runs Node.js version 20 on April 15, 2026. The upgrade process excludes any application that uses Node.js version 22 or Node.js version 24.
FAQs
Is there any action required on my part?
Yes, all environments must upgrade to Node.js 22 or later before Wednesday, April 15, 2026. Before that date, upgrade non-production applications to test for incompatibilities. Start non-production upgrades to ensure enough time for testing before the production application upgrade. After you resolve incompatibilities, upgrade the production environment before the end-of-life deadline on April 15, 2026.
For instructions to change the Node.js version, refer to Getting started with Node.js applications and environments. After April 15, 2026, the managed upgrade process moves any applications that remain on Node.js version 20 to Node.js version 22.
How can I try the latest supported version of Node.js locally?
Install the Node.js runtime locally with version 22. Refer to the Nodejs.org version calendar for download information.
Does the upgrade cause downtime for non-production environments or production applications?
Some connections receive a momentary service interruption. Applications might require code changes to ensure they operate as expected after the upgrade to Node.js version 22 or later.
Are there other resources to assist with this migration?
Is the upgrade to the latest version of Node.js available?
Acquia supports Node.js version 20 on Node Classic. Acquia supports Node.js versions 22 and 24 on Front End Hosting - Advanced.
Who can I contact for additional questions?
Contact Acquia Support for questions regarding this update.
Node.js version 20 retirement FAQ
Nodejs.org ends support for Node.js version 20 on April 30, 2026. Consequently, Acquia ends support for Node.js version 20 on Wednesday, April 15, 2026. At that time, Acquia removes Node.js version 20, and upgrades all remaining environments to Node.js version 22. This deadline is final because applications must upgrade to ensure continued security.
Acquia recommends that customers move to Node.js version 22 after appropriate testing. For applications that use Front End Hosting - Advanced, Node.js versions 22 and 24 are available.
Note
Acquia schedules managed upgrades for any application that runs Node.js version 20 on April 15, 2026. The upgrade process excludes any application that uses Node.js version 22 or Node.js version 24.
FAQs
Is there any action required on my part?
Yes, all environments must upgrade to Node.js 22 or later before Wednesday, April 15, 2026. Before that date, upgrade non-production applications to test for incompatibilities. Start non-production upgrades to ensure enough time for testing before the production application upgrade. After you resolve incompatibilities, upgrade the production environment before the end-of-life deadline on April 15, 2026.
For instructions to change the Node.js version, refer to Getting started with Node.js applications and environments. After April 15, 2026, the managed upgrade process moves any applications that remain on Node.js version 20 to Node.js version 22.
How can I try the latest supported version of Node.js locally?
Install the Node.js runtime locally with version 22. Refer to the Nodejs.org version calendar for download information.
Does the upgrade cause downtime for non-production environments or production applications?
Some connections receive a momentary service interruption. Applications might require code changes to ensure they operate as expected after the upgrade to Node.js version 22 or later.
Are there other resources to assist with this migration?
Service Offerings