Skip to main content

Upgrades & versioning

The fear behind every self-hosted update is the same: will this one break my install. Cobblr is built so the answer is no by default, and this section is how that holds up.

  • Updating: the two commands that pull a newer version and restart, and how to pin a version instead of always taking the latest.
  • Versioning and breaking changes: how versions work, what counts as breaking, and the additive-migration rule that keeps an update from rewriting your data.
  • Rollback: when an update won't come up, how to get back to the last working version.
  • Bundle upgrades: how an installed bundle updates without clobbering the fields and views you customized.

The short version: database changes are additive, so a new release adds to your schema rather than rewriting it. A change to how a field is shaped heals itself on the next start rather than asking you to uninstall and reinstall. Your customizations to a bundle live in a separate layer the bundle never overwrites. The pages here show where each of those promises is enforced.