Skip to main content

Bundle upgrades

An installed bundle is a starting point you were meant to change: hide a field, rename one, add a dropdown option, reorder the form. So the question a bundle update has to answer is, does taking a newer version wipe the customizations you made. It does not, and this page explains why.

How an update appears​

A bundle carries a version. When the marketplace holds a version newer than the one you installed, the bundle's detail panel offers Update instead of just showing it as installed. The update shows a diff of what the new version changes before you apply it, so nothing lands unseen.

Your changes live in a separate layer​

The reason an update is safe is structural. When you customize a bundle field, your change is written to a user layer, keyed by the field's stable name. The bundle only ever writes its own layer. When a form loads, Cobblr resolves the two in order and the user layer wins.

Because the bundle never writes into your layer, a new version re-pushing its own fields cannot touch what you changed. Relabels, hidden fields, reordering, and custom dropdown options survive an update by construction, with no special "preserve my edits" step to remember. "Reset to bundle default" is the reverse: it removes your override for that field and the bundle's own version shows through again.

When the update touches the same field you changed​

There is one case that needs your input: the new version changes or removes the very field you customized (it renames the field you relabelled, or drops a choice you rely on). Before applying, the update compares the incoming version against your layer and, for each field that collides, asks whether to keep yours or take the update's.

  • Keep yours is the default, and it needs no action: your layer already wins.
  • Take the update's removes your override for that field so the new version's value applies.

Only the fields that actually collide prompt. Everything else in the update lands normally.

Re-applying and no-ops​

Installing a bundle version you already have is a no-op: the pieces already present are left as they are. This makes it safe to re-run an install without worrying about duplicates.