ci: Fix CLI release workflow trigger race#2313
Merged
Merged
Conversation
The trigger wasn't being gated the same way the tag creation was which looks like was causing issues when amd64 ran before arm64. In that case we would not create a tag but still try to trigger the release workflow which would fail on missing tag. I chose to combine both steps into one instead of fixing the `if:` because there's no benefit to separating them out like they were.
samrose
approved these changes
Jul 23, 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 kind of change does this PR introduce?
Bug fix
What is the current behavior?
Sometimes the cli release workflow trigger fails when running amd64 builds. For example https://github.com/supabase/postgres/actions/runs/30005331013/job/89199985385 fails with the following message:
And it looks like that is a race where amd64 got to this stage before arm64 was able to create the tag.
What is the new behavior?
I've combined both tag and trigger release workflow into one step since they are pretty tightly coupled and also meant to be done just once.