You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docusaurus/docs/cloud/projects/settings.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -325,8 +325,11 @@ The environment's Node version is based on the one chosen at the creation of the
325
325
326
326
1. In the *Basic information* section of the <Iconname="faders" /> *Configuration* tab, click on the *Node version*'s edit <Iconname="pencil-simple" /> button.
327
327
2. Using the *Node version* drop-down in the dialog, click on the version of your choice.
328
-
3. Click on the **Save** button.
329
-
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.
328
+
3. Click on **Save**, or **Save & deploy** if you want the changes to take effect immediately.
329
+
330
+
:::tip
331
+
Ensure the Node version configured in your Strapi project matches the Node version shown in your project’s dashboard before deploying.
0 commit comments