799c7e6936
Co-authored-by: Denys Konovalov <kontakt@denyskon.de> Co-authored-by: Mathieu COSYNS <64072917+Mathieu-COSYNS@users.noreply.github.com>
26 lines
948 B
Plaintext
26 lines
948 B
Plaintext
---
|
|
group: Migration
|
|
title: Updating Your CMS
|
|
weight: 100
|
|
---
|
|
|
|
The update procedure for your CMS depends upon the method you used to install Static CMS.
|
|
|
|
## Package Manager
|
|
|
|
If you are using a package manager like Yarn or NPM, use their standard procedure to update. This is how both the Hugo and Gatsby starters are set up.
|
|
|
|
## CDN
|
|
|
|
If you are using Static CMS through a CDN like Unpkg, then that depends on the version tag you are using. You can find the version tag in the `/admin/index.html` file of your site.
|
|
|
|
- (Recommended) If you use `^4.0.0`, Static CMS does all updates except major versions automatically.
|
|
- It upgrades to `4.0.1`, `4.1.0`, `4.1.1`.
|
|
- It does not upgrade to `4.0.0` or higher.
|
|
- It does not upgrade to beta versions.
|
|
|
|
- If you use `~4.0.0`, Static CMS will do only patch updates automatically.
|
|
- It upgrades `4.0.1`, `4.0.2`.
|
|
- It does not upgrade to `4.1.0` or higher.
|
|
- It does not upgrade beta versions.
|