Is this related to a problem?
The update-service-version workflow cannot handle receiving many calls at the same time. If we trigger changes in core, it will update multiple services within a few minutes. Currently we create a branch for each update. It fails due to merge conflicts or creating duplicate tag/release versions.
Desired Solution
Use a common branch to stage changes.
Update that branch
Test
If Pass Release
Steps 3/4 should use a concurrency group and cancel-in-progress to ensure only one process is trying to create a release at a time.
Is this related to a problem? The update-service-version workflow cannot handle receiving many calls at the same time. If we trigger changes in core, it will update multiple services within a few minutes. Currently we create a branch for each update. It fails due to merge conflicts or creating duplicate tag/release versions.
Desired Solution
Steps 3/4 should use a concurrency group and
cancel-in-progressto ensure only one process is trying to create a release at a time.