Repository navigation
Add release branch Beta deployment workflow [WPB-26469] - #21648
Merged
Merged
Conversation
screendriver
requested review from
arjita-mitra,
e-maad,
otto-the-bot,
thisisamir98 and
zskhan
as code owners
June 25, 2026 04:38
screendriver
force-pushed
the
release-process
branch
3 times, most recently
from
June 25, 2026 05:10
96f1488 to
32c8f76
Compare
screendriver
enabled auto-merge
June 25, 2026 05:19
screendriver
force-pushed
the
release-process
branch
from
June 25, 2026 05:24
32c8f76 to
5f06e11
Compare
Adds the first `release-cloud` workflow step for ADR 0002. - Deploys `release/**` branches to the temporary ADR Beta mapping, currently `wire-webapp-staging` - Validates release branch names with the existing release metadata helpers - Builds one Elastic Beanstalk artifact and deploys that exact artifact to Beta - Creates annotated Beta tags only after successful Beta deployment - Runs E2E against Beta and reports results to Testiny - Keeps Production deployment and Production approval out of scope - Leaves the old tag-driven release behavior unchanged
screendriver
force-pushed
the
release-process
branch
from
June 25, 2026 05:26
5f06e11 to
7de2150
Compare
arjita-mitra
approved these changes
Jun 25, 2026
|
This was referenced Jun 25, 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
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
Adds the first release-cloud workflow step for ADR 0002.
This introduces release branch → Beta deployment automation.
Details
The workflow:
release_branchinputrelease/YYYY-MM-DD.NYYYY-MM-DD.N-beta.Monly after successful Beta deploymentDuring the transition, ADR “Beta” maps to the existing
wire-webapp-stagingenvironment.Notes
During the transition this workflow is manual-only.
It intentionally does not run automatically on
release/**yet, because the old release process is still active. This avoids surprising current release operations by deploying to the temporary Beta mapping, creating ADR-style Beta tags, running E2E, or reporting to Testiny automatically.The automatic
release/**trigger can be enabled later when the new release-cloud flow becomes the official Beta release path.Tracking
Part of #21597.
Follow-up to: