Ensure release creation only happens after release deletion is completed successfully #365
Conversation
This file contains 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
…ted successfully Signed-off-by: Jose R. Gonzalez <[email protected]>
jsm84
approved these changes
Jul 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For whatever reason, we were still seeing draft releases even after #363 explicitly set the draft bool to false.
In my testing of the workflow itself, I think what's happening is that the two jobs are running somewhat concurrently. The releaser action will make things a draft if an existing release exists so as to not clobber a release with changes. To that end, I think we if we wait for the deletion to complete, we should end up with a pre-release that isn't a draft.