Skip to content

ci: add ungated manual dev-release trigger#110

Merged
ohxyz merged 1 commit into
mainfrom
ci/manual-dev-release
Jun 29, 2026
Merged

ci: add ungated manual dev-release trigger#110
ohxyz merged 1 commit into
mainfrom
ci/manual-dev-release

Conversation

@ohxyz

@ohxyz ohxyz commented Jun 29, 2026

Copy link
Copy Markdown
Collaborator

Adds a third publish path to publish.yml so a dev-tagged build can be cut manually from any branch without the PUBLISH approval gate.

  • New dev_release boolean input on workflow_dispatch (renders as a checkbox in the Run-workflow dialog).
  • New ungated manual-dev-publish job (no environment:): checks out the branch picked in the dispatch ref dropdown, computes an ephemeral <next-patch>-dev-<sha> version (same recipe as dev-publish), and publishes under the dev tag. No git tag, no release notes.
  • Existing publish job guarded with inputs.dev_release != true so the formal latest release (box unchecked) is unchanged and still PUBLISH-gated.
  • Auto dev-publish (merged PR to main) is untouched.
  • RELEASING.md documents the new path.

Note: the new workflow_dispatch input only becomes selectable once this lands on the default branch.

Add a dev_release checkbox input to publish.yml's workflow_dispatch that
routes to a new manual-dev-publish job: publishes an ephemeral
<next-patch>-dev-<sha> under the dev tag from the selected branch, with no
PUBLISH environment gate. The existing formal publish (box unchecked) and
auto dev-publish paths are unchanged.
@ohxyz ohxyz requested a review from bhjsdev as a code owner June 29, 2026 08:09
@ohxyz ohxyz merged commit acde981 into main Jun 29, 2026
1 check passed
@ohxyz ohxyz deleted the ci/manual-dev-release branch June 29, 2026 08:10
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.

1 participant