Skip to content

Commit b256b02

Browse files
authored
Update README.md
Added a comment on patch upgrades.
1 parent d417f0e commit b256b02

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

umbraco-cloud/product-upgrades/README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,8 @@ This describes how a Umbraco Cloud project is auto-upgraded:
5757
* The failed upgrade is then tracked for reporting and the customer will be notified if necessary
5858
* 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.
5959

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 %}
61+
6062
## How do baseline updates work?
6163

6264
The upgrade process for patch and minor versions is the same for projects with child projects created off them. The difference is that we always upgrade the baseline as the first project, and afterward we upgrade the child projects. This ensures that any updates done from the baseline will also send the upgrade to the children.

0 commit comments

Comments
 (0)