fix(ci): wait for release-list propagation before resolving draft tag#163
Merged
ashishkurmi merged 1 commit intoJul 9, 2026
Conversation
GoReleaser creates the draft release for a tag pushed earlier in the same job, and GitHub can take a few seconds to index that tag before the new release shows up in the releases-list API. Querying immediately can return an empty list and fail with "Could not find draft release", even though the release was created successfully. Add a fixed 30s sleep before the lookup to give GitHub's API time to catch up.
varunsh-coder
approved these changes
Jul 9, 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.
GoReleaser creates the draft release for a tag pushed earlier in the same job, and GitHub can take a few seconds to index that tag before the new release shows up in the releases-list API. Querying immediately can return an empty list and fail with "Could not find draft release", even though the release was created successfully.
Add a fixed 30s sleep before the lookup to give GitHub's API time to catch up.
What does this PR do?
Type of change
Testing
./stepsecurity-dev-machine-guard --verbose./stepsecurity-dev-machine-guard --json | python3 -m json.toolmake lintmake testRelated Issues