Repository navigation
v0.14.0
Breaking changes
- Remove
sf cms get workspace,sf cms get channel,sf cms get content,sf cms get variant,sf cms export workspace,sf cms import workspace, andsf cms update content, without aliases. Usesf cms list workspace/sf cms list channelfor inventories andsf cms retrieve content/sf cms deploy contentfor supported portable content workflows. These are not replacements for raw details, historical versions, complete workspace backup/restore, or every legacy update operation. - Email and Email Template companions now share the definition stem: for example,
Welcome.cms-email.json,Welcome.cms-email.html, and optionalWelcome.cms-email.txt. Older role-suffixed files are not migrated automatically; back up local edits before refreshing sources.
What's new
- Retrieve supported native Images with
sf cms retrieve content, either as media bytes or an external URL-only representation. Image deployment is not included yet. - Make
sf cms infoclearer about the nine available public commands and their supported operations. - Add a beginner-friendly README covering installation, the Email download/edit/preview/apply workflow, support limits, and recovery.
Limits
- Email deployment remains limited to supported dependency-free raw HTML: Draft creation, eligible Draft HTML-only updates, or unchanged content. Deployment labels remain conservative and may still show
unqualified.
Full Changelog: v0.13.0...v0.14.0