Atomically publish revisions across multiple entities
Publishes a set of revisions — at most one per entity — across Feature Flags, Saved Groups, configs, and constants as a single all-or-nothing operation.
Validation, guards, and custom hooks run against the combined end-state of the whole set, so interdependent changes (e.g. a config schema change plus the values that depend on it) publish together even when the in-between states would be invalid.
A blocked publish returns one 422 listing every gate across every item and the flag that clears each. A concurrent change to any target aborts with a 409 and nothing publishes. A failure after the commit starts rolls everything back and emits revision.publishFailed for each revision in the set. SDK payloads refresh once per request. Pass dryRun: true for the full gate report with zero writes.
Requires the releases commercial feature.
Authorizations
If using Bearer auth, pass the Secret Key as the token:
Body
The revisions to publish, at most one per entity.
1 - 50 elements- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
Report every gate and outcome without writing anything.
Set to true to acknowledge warnings from experiment guards, schema changes, or archives. It can also force-publish an out-of-date draft when the caller has Bypass draft approvals access for that resource.
Set to true to publish despite schema or invariant failures. Validation still runs and the response still reports each failure. The caller must have Bypass draft approvals access for Feature Flags, Configs, and Constants in every Project.
Set to true to publish despite Custom Hook rejections. The caller must have Bypass draft approvals access for Feature Flags, Configs, and Constants in every Project.
An optional publish comment recorded on every revision in this release — it appears in each entity's revision history and is passed to any custom validation hooks that run for the publish.
Response
Resource created
Dry runs report every gate, cleared and blocking. Real publishes return an empty list — blocking gates fail with a 422 instead.
Gates bypassed by the caller's flags or authority — what this publish overrode.
Correlation token (pub_…) stamped on every event this publish emitted. Absent on dry runs.

