CD: Deployment tools race conditions

[L2D2Grafana]

Recently we merged some PRs to main and then immediately kicked off the cd.yml to prod as the ci.yml (which uses the cd.yml) attempted to update dev+ops. Our PRs updating dev to the new prod version were closed because it was Superseded by another PR with the same branch prefix: auto-merge/updater/grafana-lokiexplore-app-dev. This makes sense but it stopped our prod argo workflows to dev, ops, prod. Is there a different way we should configure these workflows? Like auto updating dev, ops on merge and only update prod when triggering a release. Or perhaps all the PRs to go through if they have different timestamps even if they have the same prefix.

• On PR branch merge to main, we auto deploy to github workflow

auto-merge-environments: dev,ops

• Using Cd.yml to publish to prod also updates github workflow, deployment tools PR

[ifrost]

I've faced similar issue, though it happens not only when merging other PRs to main but during release workflow (where changelog and package.json is merged to main during the workflow): #252