Retiring older versions of Node.js and Ruby

We're updating our hosting platform to use newer versions of Node.js and Ruby. Here's what's changing, why it matters, and the steps you'll need to take to get your apps ready.

Table of contents

• Why the upgrade?
• What's changing?
• How does this affect you?
• Tips for an easy upgrade
• Node.js apps
• Ruby apps
• Common issues to watch for
• What happens if I do nothing?

Why the upgrade?

Upgrading is essential for a few key reasons:

• Security: Old versions no longer receive security fixes, so moving to new ones helps protect your apps.
• Speed & performance: New releases usually have speed boosts and better reliability.
• Compatibility: Your apps must have the latest versions to keep up with new tools and libraries.
• Support: Once older versions are no longer supported, you may encounter problems or bugs that cannot be fixed.

Back to top

What's changing?

Here are the updates:

• Node.js: We're moving from Node.js LTS 10 (EOL) to Node.js LTS 24 (current).
• Ruby: Ruby version 3.2 will replace Ruby versions 2.5, 2.6, 2.7, 3.0, and 3.1.

All apps will use the newest versions with better features and security.

Back to top

How does this affect you?

If your apps are running on old Node.js or Ruby versions, you must upgrade them. This usually means updating your app's primary language and any add-ons or libraries.

Disclaimer: While our GoDaddy Guides are always here to assist with your hosting needs, we cannot help update or modify your application code. We recommend consulting with your app's developer or a web professional for assistance with code updates.

Back to top

Tips for an easy upgrade

Here are a few tips to simplify the upgrade:

• Backup first: Always save a copy of your app and database before making changes.
• Read the change logs: Check Node.js and Ruby release notes for new features or changes.
• Update everything: Ensure all your libraries and dependencies are compatible with the new versions.
• Test everything: Try your app in a test environment before going live.
• Check after launch: Once your app is up and running, monitor it to spot any issues quickly.
• Review the documentation: If you encounter problems, consult official documents, participate in community forums, or contact your app developer's support.

Back to top

Node.js apps

You'll need to get your app working with Node.js LTS 24. Make sure to update all your packages and dependencies since some older ones might not work with the new Node.js.

Simple upgrade steps:

1. Sign in to cPanel.
2. Find your Node.js apps in cPanel by typing "Node.js" in the search box.
3. Select Setup Node.js App.
4. Use the pull-down menu to select the latest Node.js version.
5. Select RESTART.

You'll need to do the following to ensure your application's compatibility:

• Check your app and its dependencies for compatibility with Node.js LTS 24. Look for migration tips from the makers of your frameworks and libraries.
• Edit your package.json file to list the correct versions.
• Run npm update to grab the latest versions of everything.
• Test your app before launching it—better safe than sorry!
• Deploy your app with Node.js LTS 24 using cPanel's Node.js Application Manager.

Back to top

Ruby apps

Apps running on Ruby must be updated to Ruby 3.2, including all gems and libraries.

Here's what to do:

1. Sign in to cPanel.
2. Find your Ruby apps in cPanel by typing "Ruby" in the search box.
3. Select Setup Ruby App.
4. Under Existing applications, use the pull-down menu to choose the most current version of Ruby.
5. Select Update and then Restart.

You'll need to do the following to ensure your application's compatibility:

• Check your code for compatibility with Ruby 3.2. Some older syntax or features might need updating.
• Update your Gemfile with the correct gem versions.
• Run bundle update to refresh all your dependencies.
• Test your app in a safe environment to make sure everything works.
• Deploy with Ruby 3.2 using the cPanel Ruby Application Manager.

Back to top

Common issues to watch for

• Dependency problems: Some older add-ons might not work with the new versions. Try updating or swapping out anything that breaks.
• Changes in syntax: Look for any old code that might not work anymore and update it.
• Environment variables: Ensure everything's set up correctly for the new runtimes.
• Config files: Update your configuration files as needed.
• Performance: Watch for speed or stability changes after upgrading, and tweak as needed.

Back to top

What happens if I do nothing?

Once these changes are live on November 10, 2025, older versions will no longer function, and these applications will be automatically updated to the new versions.

Back to top

More info

• You can find the current release status of Node.js versions on the Nodejs.org site.
• You can find the current status of Ruby maintenance branches on the ruby-lang.org site.