gcg/static-cms
0
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
static-cms/website/content/docs/update-the-cms-version.md
Shawn Erquhart 34c8c2ad70
fix(build): output aliased cms.js w/ deprecation (#1526) 
When loading Netlify CMS via script tag from a CDN, the file was named
`cms.js` until 2.0, when it was renamed to `netlify-cms.js` in alignment
with all packages outputting files that match the package name. To avoid
a lot of broken sites and confusion, this commit outputs both filenames
and prints a deprecation warning to the console in `cms.js` only.
2018-07-27 11:08:17 -04:00

980 B
Raw Blame History

title weight group
Update the CMS Version 60 start

The update procedure for your CMS depends upon the method you used to install Netlify CMS.

Package Manager

If you are using a package manager like Yarn or NPM, you will use their standard procedure to update. This is how both the Hugo and Gatsby starters are set up.

CDN

If you are using the CMS through a CDN like Unpkg, then that depends on the version tag you are using. You can find the version tag you are using in the /admin/index.html file of your site.

  • (Recommended) If you use ^2.0.0, the CMS will do all updates except major versions automatically.

    • It will upgrade to 2.0.1, 2.1.0, 2.1.2.
    • It will not upgrade to 3.0.0 or higher.
    • It will not upgrade to beta versions.

  • If you use ~2.0.0, the CMS will do only patch updates automatically.

    • It will upgrade 2.0.1, 2.0.2.
    • It will not upgrade to 2.1.0 or higher.
    • It will not upgrade beta versions.