Skip to content

feat: [CLIENT-5161] add reusable workflow to promote release bundles - #284

Open
juliannguyen4 wants to merge 14 commits into
mainfrom
jnguyen/CLIENT-5161-add-promote-release-bundle-workflow-for-qe
Open

feat: [CLIENT-5161] add reusable workflow to promote release bundles#284
juliannguyen4 wants to merge 14 commits into
mainfrom
jnguyen/CLIENT-5161-add-promote-release-bundle-workflow-for-qe

Conversation

@juliannguyen4

@juliannguyen4 juliannguyen4 commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

This allows developers to promote their release bundles to DEV and TEST, as well as QE to promote release bundles from TEST to STAGE.

Test plan

  • Have QE test this workflow from this branch
  • Python client can reuse this workflow too, but it needs to tag the release bundle in a different job now Just sticking to my own vendored copy of the workflow

TODO

  • Missing README
  • Should be documented in table of contents if applicable
  • Needs functional test

@juliannguyen4 juliannguyen4 changed the title feat: add reusable workflow to promote release bundles feat: [CLIENT-5161] add reusable workflow to promote release bundles Jul 28, 2026
@juliannguyen4
juliannguyen4 marked this pull request as ready for review July 29, 2026 14:33
@juliannguyen4
juliannguyen4 requested a review from a team as a code owner July 29, 2026 14:33
oidc-provider-name: ${{ inputs.oidc-provider-name }}
oidc-audience: ${{ inputs.oidc-audience }}

- uses: ./.github/actions/promote-release-bundle

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This workflow just wraps the action but doesn't add anything extra like validation or ensuring stages aren't skipped.

@arrowplum arrowplum left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is lacking a reason to exist other than a desire to use actions instead of workflows. I can see a place for it but only if it also adds the extra protections: Making sure it doesn't jump any stages in a promotion, making sure it satisfies any criteria, etc.

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.

3 participants