Releases
Learn Release items, states, schedules, windows, and atomic execution.
Use a Release when several whole-entry or whole-asset actions must happen together. Execution publishes every item or none.
| Term or state | Meaning |
|---|---|
| Release item | One Publish or Unpublish action for one entry or asset. |
| Release-staged version | A Publish item’s copy, edited separately from the live Draft. |
| Open | An editable plan. |
| Scheduled | An editable plan with a future run time. |
| Running | Execution is in progress. |
| Published | All actions committed. |
| Failed | Execution failed before content went live. |
| Rolled back | The pre-Release state was restored. |
| Archived | An inactive Open Release retained for reference. |
| Release window | A start and optional end that restores the pre-Release state. |
An Unpublish item targets either Draft or Archived. A Publish item carries its own staged version.
Access
Reading requires backend.read and release.read, with matching Data Type scopes. Mutations require the named Release permission, and each item action requires the applicable content.publish or content.unpublish permission.
One content item can have only one active scheduling owner. Scheduled Releases stay editable but must be validated again after changes. Published Releases are immutable; rollback runs at most once and refuses to overwrite newer published changes.