fix(ci): trigger deb.yml on release:published instead of push:tags#86
Merged
Conversation
Same fix as rpm.yml (#84): switch from push:tags to release:published so the GitHub Release is guaranteed to exist when the workflow fires. Remove the wait-and-fallback step (21 lines). Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
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.
Summary
Same fix as #84 (rpm.yml): switch trigger from
push: tagstorelease: publishedand remove the wait-and-fallback step.deb.yml has been working because it runs on
ubuntu-24.04(not a container), soghcan discover the repository via git. However, the timing race — workflow fires before release-please creates the GitHub Release — is the same structural risk.Changes
push: tags→release: publishedif: github.event_name == 'release'condition🤖 Generated with Claude Code