Allow publishing from release branches#555
Merged
Xavier Fortin (xfortin-devolutions) merged 4 commits intoJun 18, 2026
Merged
Conversation
The comment referenced the removed non-master 'publish-test' case; reword it to reflect that scheduled jobs always skip publishing. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Samuel Bergeron-Drouin (Samuel-B-D)
approved these changes
Jun 18, 2026
Dion Gionet Mallet (dion-gionet)
approved these changes
Jun 18, 2026
Xavier Fortin (xfortin-devolutions)
merged commit 6ca9ed3
into
master
2 of 3 checks passed
Xavier Fortin (xfortin-devolutions)
deleted the
allow-publishing-release-branches
branch
Anna Malchow-Perryman (apman)
pushed a commit
that referenced
this pull request
Jun 18, 2026
## Summary
Enables publishing a release from `release/*` branches (and `master`),
instead of being restricted to `master` only.
## Changes to `.github/workflows/build-package.yml`
- **Add a `build-branch` input** (free-text, default `master`) so the
branch to build from is chosen explicitly rather than relying solely on
the Actions UI ref picker. It's validated in preflight and must be
`master` or `release/*` (`^release/.+`), otherwise the run fails fast
with a clear error.
- **Remove the hardcoded master-only publish gate.** Previously, a
non-master, non-prerelease dispatch was force-skipped from publishing.
Now a manual dispatch can publish from the selected branch; scheduled
cron runs still always skip publishing.
- **Check out the chosen branch** explicitly (`actions/checkout` with
`ref: ${{ needs.preflight.outputs.build-branch }}`), so the packaged
code matches `build-branch`.
- Drop `(Master only)` from the publish-mode option labels (and update
the matching comparison) since the restriction no longer applies.
- Report the selected branch in the run notices.
## Notes / caveats
- The prerelease-suffix functionality is unchanged.
## Screenshots
<img width="335" height="637" alt="PusblishPopup"
src="https://github.com/user-attachments/assets/2cb21a9c-543e-4edc-a4af-9231149fab43"
/>
---------
Co-authored-by: Claude Opus 4.8 (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
3 participants
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
Enables publishing a release from
release/*branches (andmaster), instead of being restricted tomasteronly.Changes to
.github/workflows/build-package.ymlbuild-branchinput (free-text, defaultmaster) so the branch to build from is chosen explicitly rather than relying solely on the Actions UI ref picker. It's validated in preflight and must bemasterorrelease/*(^release/.+), otherwise the run fails fast with a clear error.actions/checkoutwithref: ${{ needs.preflight.outputs.build-branch }}), so the packaged code matchesbuild-branch.(Master only)from the publish-mode option labels (and update the matching comparison) since the restriction no longer applies.Notes / caveats
Screenshots