Skip to content

docs: correct deploy_success response contract for dedup behavior (WIZ-10935)#170

Open
Simon Ingeson (smonn) wants to merge 1 commit into
mainfrom
wiz-10935-docs-correct-deploy-success-response-contract
Open

docs: correct deploy_success response contract for dedup behavior (WIZ-10935)#170
Simon Ingeson (smonn) wants to merge 1 commit into
mainfrom
wiz-10935-docs-correct-deploy-success-response-contract

Conversation

@smonn

@smonn Simon Ingeson (smonn) commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

Corrects the deploy_success response contract for the dedup change (WIZ-10705 / WIZ-10728): a suite is pre-allocated and created_suite_id is returned even for deduplicated triggers. Dedup is now surfaced via green-light supersession, not duplicate_suite_id in the synchronous response. duplicate_suite_id is scoped to same-sha retries after dedup has settled.

Draft, do not merge. Gated on the rollout / WIZ-10891 announcement (flag default off).

WIZ-10935

The dedup change pre-allocates a suite and returns created_suite_id even
for deduplicated triggers; dedup is settled asynchronously after the 200
and surfaced via green-light supersession, not duplicate_suite_id in the
synchronous response. Scope the duplicate_suite_id case to same-sha
retries after dedup has settled.

WIZ-10935
@smonn Simon Ingeson (smonn) marked this pull request as ready for review June 30, 2026 20:05
@mintlify

mintlify Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
qawolf 🟢 Ready View Preview Jun 30, 2026, 8:17 PM

@JohnGluck

Copy link
Copy Markdown
Collaborator

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants