NewImprovedFixed

v2.9.12

Node.js 26 LTS, Clearer Release Mode Messages and a Working Fix with AI for Vulnerable Sites

You can now run Node.js 26 LTS on your servers. When Release mode can’t be used on a site, it now tells you why and what to do next. Fix with AI on the known vulnerabilities card in the To-Do Center now updates the plugins and themes that have a fix, and the card shows that the assistant is working.

🔥 New Features

🆕 Run Your Apps on Node.js 26 LTS

Node.js 26 became the newest long-term support version in October 2026. Before, the newest version you could pick was Node.js 24. Now you can choose Node.js 26 for your server.

Who it’s for: Developers who host Node.js apps on xCloud.

  • Open your server → Node Configuration, pick 26 under Default Node.js Version and click Save Changes. xCloud installs it in the background.
  • Nothing changes on your existing servers. They keep the Node.js version they run until you change it.
  • New installs still use Node.js 24 when no version is chosen.
  • The Security Center shows Security update available for Node.js 26 older than 26.12.1, the first version with the latest security fixes.
  • The end-of-life email now suggests testing your app on Node.js 22, 24 or 26 first.

How to Change Node Version with xCloud

🧑‍💻 For Developers: Public API and MCP

  • Node.js versions: GET /servers/{uuid}/node-versions now lists 26, and you can install Node.js 26 through the Public API and MCP. Versions 25 and 27 are still refused with a 422.
  • Release mode refusals: the Public API and MCP return the new Release mode messages in their 422 responses.

⚡ Improvements

Release Mode Tells You What to Do Next

Before, when Release mode couldn’t be turned on for a site, the message was short and didn’t say what to do. Now each message says what isn’t available, why, and what to do next. The rules for which sites can use Release mode have not changed.

Who it’s for: Developers who deploy from Git, including Node.js, WordPress and Docker sites.

  • On a Node.js site on an OpenLiteSpeed server, the Git settings now say: “Release mode is not available for Node.js sites on OpenLiteSpeed servers. It works on nginx servers, so host this site on an nginx server to use it.” WordPress sites from Git get the same kind of message.
  • On a Docker site that runs its own docker-compose file, the message now says: “Zero-downtime deploys don’t work yet for sites that use their own docker-compose file. Your site keeps deploying normally, with a short restart. Sites built from a Dockerfile can use it today.” Before, it read as if your compose file was broken.
  • When you create a Docker site, a short note says that sites built from a Dockerfile can turn on zero-downtime deploys after creation under Git settings.
  • Messages for other site types, other server types, sites not deployed from Git, more than one public port and a custom deploy script follow the same pattern.

Release Mode Messages and Fixes in xCloud

🐞 Bug Fixes

  • To-Do Center
    • Fix with AI on the known vulnerabilities card (for example 3 sites have known vulnerabilities) now works. The assistant reads the known vulnerabilities on each site, asks you to approve one update per site, and updates only the plugins and themes that have a fixed version. It tells you plainly when no fix exists yet. Before, it kept checking updates and backups for each site, then gave up. How to Use the To-Do Center in xCloud
    • After you click Fix with AI, the card now shows Working on it in the assistant with a button that opens the chat. Before, the card showed nothing.
    • When you give the assistant access, it no longer says the To-Do item is closed.
  • AI Assistant
    • The assistant now checks how a WordPress update ended before it reports success. A failed update is reported as failed.
    • You now get one outcome message per update, not two. If an update reported as failed later succeeds, the assistant posts one correction.