fix(ci): trigger release build on release publish, not tag push#40
Merged
Conversation
semantic-release creates the tag via the GitHub Releases API (@semantic-release/github). API-created tags don't emit the refs/tags/* push event that 'on: push: tags' listens for, so the artifact build never auto-ran — every release so far was built by manual workflow_dispatch. The PAT-published release does fire 'release: published', so trigger on that. workflow_dispatch stays as a manual fallback.
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 Tauri artifact build (
release.yml) has never auto-triggered — all historical runs are manualworkflow_dispatch. v0.12.0 shipped with zero assets until hand-dispatched.Root cause
@semantic-release/githubcreates the tag via the GitHub Releases API. API-created tags don't emit therefs/tags/*push event thaton: push: tags: ['v*']listens for. (TheRELEASE_TOKENis a real PAT — verified: v0.12.0's release author isoffendingcommit, not a bot — so the token was never the issue.)Fix
Trigger on
release: published, which the PAT-published release does fire.workflow_dispatchstays as a manual fallback. Existing steps already resolvegithub.ref_name/github.refto the tag on a release event, so no step changes needed.Verification
Next release will auto-build artifacts on publish. (v0.12.0 is being backfilled by an in-flight manual dispatch.)