modelcontextprotocol/registry
Watch
1
0
Fork
You've already forked registry
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ci: Add concurrency groups to prevent deployment conflicts (#381)

Browse source 
## Summary

Add per-environment concurrency groups to staging and production
deployment jobs to prevent Pulumi stack lock conflicts when multiple PRs
are merged simultaneously.

- `deploy-staging` job gets `deploy-staging` concurrency group
- `deploy-production` job gets `deploy-production` concurrency group  
- Both use `cancel-in-progress: false` to queue deployments safely

This eliminates CI noise from failed parallel deployments while
maintaining deployment reliability.

Fixes #375
This commit is contained in:
adam jones 2025-09-08 17:34:27 -07:00 • committed by GitHub
commit da2965f6e2
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 6 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
.github/workflows/deploy.yml vendored
View file

@ -56,6 +56,9 @@ jobs:
runs-on: ubuntu-latest runs-on: ubuntu-latest
environment: staging environment: staging
needs: docker-push needs: docker-push
concurrency:
group: deploy-staging
cancel-in-progress: false
steps: steps:
- name: Checkout code - name: Checkout code
uses: actions/checkout@v4 uses: actions/checkout@v4
@ -92,6 +95,9 @@ jobs:
runs-on: ubuntu-latest runs-on: ubuntu-latest
environment: production environment: production
needs: deploy-staging needs: deploy-staging
concurrency:
group: deploy-production
cancel-in-progress: false
steps: steps:
- name: Checkout code - name: Checkout code
uses: actions/checkout@v4 uses: actions/checkout@v4