Deployment & Release
The service deploys to Cloud Run through GitHub Actions. Staging deploys on every merge; production deploys when a release is tagged.
| Environment | Trigger | Workflow |
|---|---|---|
| Staging | Merge to main | Build and Deploy Staging |
| Production | A vX.Y.Z tag is pushed | Build and Deploy Production |
Changes to markdown files alone don't trigger a staging deploy.
Every pull request and every deploy runs Biome, the type check and the tests first. A failure stops the deploy.
Releasing to productionβ
- In GitHub Actions, run π·οΈ Tag new release on
mainand pick Patch, Minor or Major. - The workflow creates the next version tag and a GitHub release.
- The tag starts Build and Deploy Production, which also writes the release notes.
Configurationβ
The deploy only sets a few variables. Credentials and other settings live on the Cloud Run service itself, so a new variable has to be added there by hand in each project.
Monitoringβ
Production has four alert policies in Cloud Monitoring:
- Catalog API uptime failure
- Catalog API 5xx errors
- Catalog API authorizer failures
- Catalog API serving stale taxonomy
Staging has no alerts.