Skip to content

fix: add concurrency group to DEV deploy workflow#3584

Merged
TaprootFreak merged 1 commit intodevelopfrom
fix/dev-deploy-concurrency
Apr 20, 2026
Merged

fix: add concurrency group to DEV deploy workflow#3584
TaprootFreak merged 1 commit intodevelopfrom
fix/dev-deploy-concurrency

Conversation

@TaprootFreak
Copy link
Copy Markdown
Collaborator

@TaprootFreak TaprootFreak commented Apr 20, 2026

Summary

  • Adds concurrency group with cancel-in-progress: true to the DEV deploy workflow
  • Fixes race condition where rapid successive pushes to develop trigger parallel Azure deploys, but only the first takes effect (Azure silently drops subsequent concurrent deploys)
  • Root cause of PR #3583 CI failure: 3 commits in 3 minutes → 3 parallel deploys → DEV stuck on b746ca6 while d3ded0c and b2e4666 were lost

Test plan

  • Push two rapid commits to develop, verify only the latest deploy runs
  • Confirm verify step passes for the surviving run

@TaprootFreak
fix: add concurrency group to DEV deploy workflow
18836e6 
Prevents race conditions when multiple commits are pushed to develop
in quick succession. Without this, parallel deploys to Azure App Service
cause only the first to take effect while subsequent deploys are silently
lost, leaving DEV on a stale commit.
@TaprootFreak TaprootFreak marked this pull request as ready for review April 20, 2026 08:28
@TaprootFreak TaprootFreak merged commit adef391 into develop Apr 20, 2026
7 checks passed
@TaprootFreak TaprootFreak deleted the fix/dev-deploy-concurrency branch April 20, 2026 08:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@davidleomay davidleomay davidleomay approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@TaprootFreak @davidleomay