Skip to content

Commit dbd4928

Browse files
authored
fix: update release action to match new registry-server dev flow (#171)
## Description This PR updates the CI release flow to match the registry-server's new development flow. The "dev" registry now deploys directly from the main branch of registry-server. The "production" registry now deploys from tagged releases of registry-server. We have added a "production" tag that will track the same commit as the latest semver release of the registry-server. --- ## Type of Change - [ ] New module - [x] Bug fix - [ ] Feature/enhancement - [ ] Documentation - [ ] Other --- ## Related Issues Fixes #170 Closes #
1 parent a1cea02 commit dbd4928

File tree

1 file changed

+2
-5
lines changed

1 file changed

+2
-5
lines changed

.github/workflows/deploy-registry.yaml

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -28,8 +28,5 @@ jobs:
2828
uses: google-github-actions/setup-gcloud@77e7a554d41e2ee56fc945c52dfd3f33d12def9a
2929
- name: Deploy to dev.registry.coder.com
3030
run: gcloud builds triggers run 29818181-126d-4f8a-a937-f228b27d3d34 --branch main
31-
# garrett!: We don't have a good way to target this right now, so I'm commenting it out
32-
# so we don't accidently deploy to production.
33-
# - name: Deploy to registry.coder.com
34-
# run: |
35-
# gcloud builds triggers run 106610ff-41fb-4bd0-90a2-7643583fb9c0 --branch main
31+
- name: Deploy to registry.coder.com
32+
run: gcloud builds triggers run 106610ff-41fb-4bd0-90a2-7643583fb9c0 --tag production

0 commit comments

Comments
 (0)