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: umbraco-cloud/product-upgrades/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ This describes how a Umbraco Cloud project is auto-upgraded:
57
57
* The failed upgrade is then tracked for reporting and the customer will be notified if necessary
58
58
* When the Dev site is upgraded successfully, the upgrader will continue this same process for the next environment in the chain (that is Dev -> Staging -> Live) depending on the number of environments that exist for the project.
59
59
60
-
{% hint style="info" %} Please note that changes for patches might appear on Development, even if the same changes have been added to Live already. This is due to the environments not being synchronized during the upgrade process, as this risks pushing something from one environment to another which is not intended. Those changes just needs to be deployed and the environments are in sync again. {% endhint %}
60
+
{% hint style="info" %} Note that changes for patches might appear on Development, even if they have already been applied to Live. The environments will not be synchronized during the upgrade process. This is because synchronization risks pushing other apparent changes from one environment to another. Those changes will need to be deployed. Once that has been done, the environments will be in sync again. {% endhint %}
0 commit comments