chore(release): Ensure only 1 release please workflow runs at the same time#2896
Merged
kodiakhq[bot] merged 2 commits intocloudquery:mainfrom Oct 16, 2022
Merged
Conversation
yevgenypats
approved these changes
Oct 16, 2022
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.
Summary
Having multiple release please workflows running at the same time can lead to race conditions where 2 workflows think they need to create release PRs.
This change ensures only one runs at the same time, visit https://docs.github.com/en/actions/using-jobs/using-concurrency for more information.
This issue is more evident in the monorepo where release please takes longer to process all releases. In small repos it's fast enough so this is not an issue