Repository navigation
chore(pipeline): SUPERSEDED execution mode (approve latest commit once) - #7
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
With
ExecutionMode.QUEUED, every push tomaincreates its own pipeline execution that runs sequentially and each stops at theApproveProductionmanual approval. A burst of commits means approving each one individually.Change
infra/pipeline/frontend-pipeline-stack.ts:ExecutionMode.QUEUED→ExecutionMode.SUPERSEDED.In SUPERSEDED mode a newer execution supersedes an older one waiting at the manual approval, so 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.
Verification
npm run lint(tsc --noEmit): passnpm run synth:pipeline: pass; synthesized template shows"ExecutionMode": "SUPERSEDED"Apply note
The pipeline is intentionally not self-mutating: merging this does not reconfigure the pipeline. It is applied manually via
npm run deploy:pipelinewith frontend-account admin credentials after reviewingnpm run diff:pipeline.