- ⚠️ SECURITY UPDATE: Fixed a medium-severity vulnerability in the Editorial Workflow that let unreviewed changes be merged along with an entry. The CMS showed a reviewer one entry, but publishing merged the whole pull or merge request behind it, so anything else on its branch — a change to the site’s code, a CI workflow, another entry — went live unseen. Both the GitHub and the GitLab backends were affected.
- Publishing an entry now checks its pull or merge request first. It has to go to the configured branch, still point at the commit the entry was loaded or saved at, and change nothing the CMS doesn’t account for; otherwise the publish is refused, saying why. The merge is then pinned to the commit that was checked. See Checks Before Publishing.
- Saving an entry onto a branch that already has an open request the Editorial Workflow board doesn’t show is now refused, rather than committing the entry into it. See Sharing a Branch.
- An entry’s workflow branch is named after the entry, not the editor, so two people working on the same entry share it. Saving now asks before writing over a change someone else has made to the entry on that branch, as it already did on the configured branch. See Conflict Resolution. This effectively solves decaporg/decap-cms#3814.
- The files in a folder named
adminorcmsare now read-only in the Asset Library and the File/Image field picker, as the CMS itself is usually served from such a folder. With a media folder at the root of the public folder, such asstatic, the CMS’s own admin page and configuration file could otherwise be replaced as assets. See Read-Only Folders. - With Open Authoring on GitHub, an entry sent for review now shows its deploy preview link and build state, which a contribution from a fork previously lacked.
- Bug fixes and improvements.
As always, we recommend using the latest version of Sveltia CMS to benefit from improvements.
Full Changelog: v0.230.0...v0.230.1