Skip to content

Batching and publishing with changesets

A changeset batches items into one atomic publish or rollback — rollback returns items to draft rather than restoring what was live before.

A changeset is a batch of content changes — creates, updates, deletes — that releases as one unit instead of one page at a time. Everything in it goes live together, or none of it does.

Publishing is one transaction

If any item in the batch fails to apply, the whole publish rolls back — not just the item that failed. A changeset either goes live in full or stays exactly where it was; there’s no partially-published state to clean up after.

An item added to a changeset can carry a specific captured version, or none. One with no version attached simply flips the page it targets to published as-is — a “make this live” with nothing new to apply. One that carries a version applies that captured snapshot onto the page first, then publishes it — which is what lets a changeset ship an edit that was saved earlier, not only whatever the page happens to hold right now.

Who can build and publish one

Creating a changeset, adding items to it, publishing it, and rolling it back all take an editor role or above, scoped to the changeset’s own site. This isn’t a site-admin-only capability despite sitting on a governing surface — see Roles and the capability matrix for the full picture.