fix: dispatch release.yml explicitly since GITHUB_TOKEN tag pushes don't trigger it#4
Merged
Merged
Conversation
Confirmed live: merging PR #3 pushed tag v0.3.0 correctly, but release.yml never ran and no GitHub Release was created. Root cause is a documented GitHub Actions behavior -- a tag pushed using the default GITHUB_TOKEN from within a workflow run does not trigger other workflows' push events, to prevent infinite loops. That exemption does not apply to workflow_dispatch, so tag-release now explicitly dispatches release.yml instead of relying on push:tags. release.yml's workflow_dispatch trigger only exists on main, not on the tag itself, and softprops/action-gh-release can't infer the right tag from a workflow_dispatch context (it falls back to github.ref_name, which would be "main"). So the dispatch passes an explicit tag input, and both the checkout step and the release step use it to check out and tag the correct ref.
shrey150
force-pushed
the
shrey/fix-tag-release-trigger
branch
from
July 16, 2026 17:05
5de6d63 to
9e52847
Compare
Kylejeong2
approved these changes
Jul 16, 2026
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
2 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.
What
Merging #3 pushed tag `v0.3.0` correctly (confirmed via `gh api repos/browserbase/browse-plugin/tags`), but `release.yml` never ran and no GitHub Release exists for it — confirmed zero workflow runs of any kind were queued for that tag push, not a failed run.
Why
Documented GitHub Actions behavior: a tag pushed using the default `GITHUB_TOKEN` from within a workflow run does not trigger other workflows' `push` events (loop prevention). `tag-release`'s tag push falls into exactly this case. The one documented exemption is `workflow_dispatch`, which `GITHUB_TOKEN` can trigger.
Fix
E2E Test Matrix
🤖 Generated with Claude Code