From 04ad26cf1c7a9bd8e87d48f4efa35d3f803a8de2 Mon Sep 17 00:00:00 2001 From: mariekirsch Date: Wed, 12 Nov 2025 18:22:41 +0100 Subject: [PATCH] chore: save & deploy for Node version --- docusaurus/docs/cloud/projects/settings.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docusaurus/docs/cloud/projects/settings.md b/docusaurus/docs/cloud/projects/settings.md index d8da5b4eec..a9a11a28d6 100644 --- a/docusaurus/docs/cloud/projects/settings.md +++ b/docusaurus/docs/cloud/projects/settings.md @@ -325,8 +325,11 @@ The environment's Node version is based on the one chosen at the creation of the 1. In the *Basic information* section of the *Configuration* tab, click on the *Node version*'s edit button. 2. Using the *Node version* drop-down in the dialog, click on the version of your choice. -3. Click on the **Save** button. -4. Trigger a new deployment in the environment for which you changed the Node version. If the deployment fails, it is because the Node version doesn't match the version of your Strapi project. You will have to switch to the other Node version and re-deploy your project again. +3. Click on **Save**, or **Save & deploy** if you want the changes to take effect immediately. + +:::tip +Ensure the Node version configured in your Strapi project matches the Node version shown in your project’s dashboard before deploying. +::: #### Editing Git branch