Add Production promotion to release-cloud workflow [WPB-26469]#21664
Merged
Conversation
screendriver
requested review from
arjita-mitra,
e-maad,
otto-the-bot,
thisisamir98 and
zskhan
as code owners
screendriver
force-pushed
the
release-process
branch
from
8be2969 to
05da7f6
Compare
zskhan
reviewed
Jun 29, 2026
Extend the release-cloud workflow with optional Production promotion for ADR 0002. The workflow now supports promoting the Beta-tested artifact to Production after successful Beta deployment and E2E validation. Production promotion is opt-in during the transition so Beta-only workflow runs do not request Production approval. When promotion is requested, the workflow performs a Production preflight, checks the Beta tag, computes the Production tag, and decides whether Production deployment is required. Production deployment waits for the wire-webapp-prod GitHub Environment approval and deploys the same artifact that was previously deployed to Beta. It does not rebuild from source. After a successful Production deployment, the workflow creates the YYYY-MM-DD.N-production tag for the selected release commit. The workflow skips Production deployment when promotion was not requested or when the matching Production tag already points to the selected release commit. It fails if the Production tag exists for a different commit. This commit does not change the old tag-driven release path, rollback, maintenance releases, Docker publishing, Helm publishing, or wire-builds behavior.
screendriver
force-pushed
the
release-process
branch
from
05da7f6 to
bad82b6
Compare
screendriver
force-pushed
the
release-process
branch
from
bad82b6 to
a3c180b
Compare
zskhan
approved these changes
Jun 29, 2026
|
This was referenced Jun 29, 2026
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
2 participants
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.
Summary
Extends the release-cloud workflow with optional Production promotion for ADR 0002.
The workflow can now promote the Beta-tested artifact to Production after successful Beta deployment and E2E validation.
Details
This extends
.github/workflows/release-cloud.yml.The workflow now:
promote_to_productioninputYYYY-MM-DD.N-productiontagwire-webapp-prodGitHub Environment approvalNotes
This pull request intentionally does not rebuild from source for Production.
Production promotion is opt-in during the transition so Beta-only workflow runs do not request Production approval.
This pull request also does not change:
wire-buildsupdatesThe Production approval gate is enforced through the
wire-webapp-prodGitHub Environment settings.Tracking
Part of #21597.
Follow-up to: