chore: limit concurrency on releases #2318
Conversation
DanielMSchmidt
requested review from
mutahhir and
Maed223
and removed request for
a team
.github/workflows/release.yml
Outdated
| @@ -15,6 +15,10 @@ env: | |||
| SENTRY_ORG: hashicorp | |||
| SENTRY_PROJECT: cdktf-cli | |||
|
|
|||
| concurrency: | |||
| group: release | |||
| cancel-in-progress: true | |||
There was a problem hiding this comment.
Can't this be dangerous? 😅
If something is merged while a release is running? Is there something we can do to safeguard that case other than "don't merge while we release a new version" 😄
There was a problem hiding this comment.
Great point! I looked it up and the default is what we want. TL;DR: no canceling, everything else gets queued, if there is already something queued only the last one gets executed, the rest skipped.
|
I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
No description provided.