Add release-branch CI config for 2.x#170
Merged
Merged
Conversation
Tell build-and-publish to treat both master and 2.x as release branches, so pushes to this maintenance branch are recognised as release-branch builds. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
Companion to #169. Adds the same
releaseBranch:block on2.xso the release-tools action — which readsreleaseBranch:from each branch's own workflow file — recognises pushes to2.xas release-branch builds.No other Step-2 changes from #169 are copied here (no version bump, no docgen change, no
versions.json); per the app-booster reference those are master-only.Test plan
2.x).2.xis classified as a release branch (build.outputs.release == 'true').