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.
Gateway registrationβ
A new endpoint needs the service registered with the gateway's authorizer again. Run π Register service for Authorization in GitHub Actions after the deploy that adds it.
Configurationβ
The deploy workflows set most variables, including the gateway matcher, Redis and the Gemini project, so changing one is a pull request to the workflow. API_GATEWAY_BASE_URL and API_GATEWAY_KEY are set on the Cloud Run service directly, and deploys keep them.
Monitoringβ
There are no Cloud Monitoring alert policies for this service, and Sentry isn't configured. Request logs are in Cloud Logging.