ci: allow release build via workflow_dispatch#18
Merged
Conversation
The Release workflow only triggered on `push: tags`, but release-please creates tags with the default GITHUB_TOKEN, which does not trigger downstream workflows. As a result no binary/Homebrew formula has been published since v0.2.0. Add a workflow_dispatch input (tag) and use it for checkout ref, version, and the release upload target so any tag can be (re)built manually.
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.
Problem
The
Releaseworkflow (release.yml) only triggers onpush: tags: v*. Since the switch to release-please (v0.2.1+), tags are created with the defaultGITHUB_TOKEN, which does not trigger downstream workflows. Consequently no macOS binary tarball or Homebrew formula update has been published since v0.2.0 —brew install mockeris stale.Fix
workflow_dispatchwith ataginput.${{ inputs.tag || github.ref_name }}for the checkoutref, theVERSION/tarball name, and thesoftprops/action-gh-releasetag_name.This lets any tag be (re)built and published manually — including back-filling v0.3.2 — while keeping the automatic tag-push trigger intact.
After merge
Dispatch for v0.3.2:
gh workflow run release.yml -f tag=v0.3.2