ci(release): drop the retired beta branch from every workflow trigger - #628
Merged
Conversation
The beta channel closed with the 1.0 release; the branch is deleted and archived as the archive/beta tag. Remove it from the package, CLI, CI, DB-integration and E2E-smoke workflow triggers, delete the beta-only publish script, and give the release/** branches the two gates beta had.
Contributor
Author
|
🎉 This PR is included in version 1.0.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
therealbrad
added a commit
that referenced
this pull request
Sep 9, 2026
Brings #628 (beta dropped from every workflow trigger), the 1.0.4 release (#630, already on this line by cherry-pick) and #629 (Jira issue panel). Resolutions: package.json keeps 1.1.0-beta.0; db-integration.yml drops beta from its push triggers and keeps this line's comment; testCaseImport.test.ts keeps this line's copy of the NaN test, which lives in the version-snapshot suite; app.jsx combines this line's live/deleted split with #629's rule that a deleted case is listed only while it still carries result history.
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
1 participant
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.
Description
The
betabranch was retired after 1.0.3 shipped (its tip is preserved as thearchive/betatag). This removes it from every workflow that still triggered on it and deletes the beta-only publish path:packages-release.yml: drop thebetapush trigger and the "Publish beta pre-releases" step; delete.github/scripts/packages-publish-beta.mjs, which nothing else referenced.cli-semantic-release.yml+cli/.releaserc.json: drop thebetaprerelease branch.ci.yml: dropbeta; pull requests intorelease/**now run CI like pushes to those branches already did.db-integration.yml+e2e-smoke.yml:betareplaced withrelease/**, so the release line keeps the two gates the beta integration line had.packages/RELEASING.md: remove the beta pre-release section and the "both branches" trigger note.No
testplanit/**path changes, so this does not trigger an app release.Related Issue
None.
Type of Change
How Has This Been Tested?
Describe the tests you ran to verify your changes:
Every edited workflow parses as YAML with the expected
on.push.brancheslist,cli/.releaserc.jsonparses, and a grep of.github/finds no remaining reference to thebetabranch (the tag-triggeredbeta-prerelease.ymlis untouched; it keys onv*-beta.*tags, not the branch).Test Configuration:
Checklist
Screenshots (if applicable)
n/a
Additional Notes
Open question for review:
db-integration.ymlande2e-smoke.ymlgainedrelease/**as a push trigger in beta's place. Drop that if the release branches should stay pull-request-gated only.