Skip to content

Add release branch Beta deployment workflow [WPB-26469] - #21648

Merged
screendriver merged 1 commit into
devfrom
release-process
Jun 25, 2026
Merged

screendriver merged 1 commit into
devfrom
release-process

Conversation

@screendriver

@screendriver screendriver commented Jun 25, 2026 •

Copy link
Copy Markdown
Member
TaskWPB-26469 [Web] Use a trunk-based automated release process

Summary

Adds the first release-cloud workflow step for ADR 0002.

This introduces release branch → Beta deployment automation.

Details

The workflow:

  • is manually triggered during the transition
  • accepts an explicit release_branch input
  • validates release/YYYY-MM-DD.N
  • builds the release artifact once
  • deploys the artifact to the temporary Beta mapping
  • creates YYYY-MM-DD.N-beta.M only after successful Beta deployment
  • runs E2E against Beta
  • reports E2E results to Testiny

During the transition, ADR “Beta” maps to the existing wire-webapp-staging environment.

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:

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
screendriver added this pull request to the merge queue Jun 25, 2026
Merged via the queue into dev with commit ab135c8 Jun 25, 2026
12 checks passed
@screendriver
screendriver deleted the release-process branch June 25, 2026 16:24
@sonarqubecloud

Copy link
Copy Markdown

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants