Skip to content

Conversation

f0ssel
Copy link
Collaborator

@f0ssel f0ssel commented Jul 2, 2025

Reverts #168 which should not have been merged, and disables production deployments for now until a fix is in place on the registry-server side.

Reverts #168 which should not have been merged, and disables production deployments for now until a fix is in place on the registry-server side.
@f0ssel f0ssel requested a review from Parkreiner July 2, 2025 14:25
@f0ssel f0ssel merged commit a1cea02 into main Jul 2, 2025
3 of 4 checks passed
@f0ssel f0ssel deleted the f0ssel/disable-prod branch July 2, 2025 14:30
bcpeinhardt added a commit that referenced this pull request Jul 2, 2025
## 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 #
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants