Why update from a Publish Branch?

Last modified: June 3rd, 2026

On this page

When a Team Member publishes new changes to your Publish Branch from another Site (or from outside CloudCannon), CloudCannon will prompt you to update your Site.

The Publishing page shows an Updates available from your Publish Branch notice, and a small down-arrow icon appears next to the Publishing link in the Site Navigation.

A screenshot of the Publishing page shows an Updates available from your Publish Branch notice with an Update from Publish Branch button.

CloudCannon doesn't automatically update your Site when the upstream Publish Branch receives new changes; you choose when to update. Updating pulls those new changes from the Publish Branch into your Site.

Updating regularly keeps your Site up-to-date with the work published by other Team Members, or by you from another Site. Your branched Site started as a copy of its Publish Branch, and updating keeps it close to that source except for the parts you have intentionally changed. Without updating, your Site will fall behind.

For instructions on updating your Site, please read our documentation on updating from a Publish Branch.

CloudCannon requires you to update from your Publish Branch before you are allowed to publish the changes on your Site, but you can update your Site whenever there are upstream changes available — even if you aren't ready to publish yet. Update your Site regularly to stay in sync with upstream changes.

For more information about publishing, please read our documentation on what publishing is.

Publishing Conflicts#

If the same file has been changed on both your Site and your Publish Branch since you last updated, CloudCannon will detect a Publishing Conflict and pause the update. You will need to choose which version of the file to keep before the update can complete. For more information, please read our documentation on what Publishing Conflicts are and how to resolve them.

Related Resources

Open in a new tab