fix(ci): release canaries from selected branches#742
Open
natew wants to merge 1 commit into
Open
Conversation
Agentbus-Session: ab-mrr25td1-78874
|
🚅 Deployed to the one-pr-742 environment in onestack.dev
|
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.
Canary workflow dispatches currently reject every non-main ref and then push the generated canary version commit to main.
This keeps patch/minor/major releases main-only, validates the selected branch tip for canaries, dispatches CI on that branch when needed, and skips the release-commit push for canaries. The package publish remains an explicit manual workflow action.
Validation: