From d991ba24389dac5710cc1ab0f8c7c4475ce1d3ce Mon Sep 17 00:00:00 2001 From: Pushp Date: Thu, 22 Oct 2026 15:10:58 +0530 Subject: [PATCH] chore(pipeline): use SUPERSEDED execution mode for production pipeline In QUEUED mode every push to main created a separate execution that each stopped at the ApproveProduction manual approval, forcing the approver to approve every commit one by one. SUPERSEDED collapses a burst of pushes so the newest execution supersedes an older one waiting at approval: the approver approves the latest commit once. Intermediate commits are not deployed individually - only the latest tested assembly reaches production, which is the desired behaviour for the static frontend. --- infra/pipeline/frontend-pipeline-stack.ts | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/infra/pipeline/frontend-pipeline-stack.ts b/infra/pipeline/frontend-pipeline-stack.ts index f0a0498..bb9e54d 100644 --- a/infra/pipeline/frontend-pipeline-stack.ts +++ b/infra/pipeline/frontend-pipeline-stack.ts @@ -114,7 +114,12 @@ export class FrontendPipelineStack extends Stack { const pipeline = new Pipeline(this, 'Pipeline', { pipelineName: 'OneHook-Frontend', pipelineType: PipelineType.V2, - executionMode: ExecutionMode.QUEUED, + // SUPERSEDED: a burst of pushes to main collapses so the newest execution + // supersedes any older one still waiting at the ApproveProduction manual + // approval. The approver approves the latest commit once, instead of + // approving every commit one by one. Intermediate commits are not deployed + // individually - only the latest tested assembly reaches production. + executionMode: ExecutionMode.SUPERSEDED, artifactBucket, restartExecutionOnUpdate: false, });