Skip to main content

Deployment & Release

The service deploys to Cloud Run through GitHub Actions. Staging deploys on every merge; production deploys when a release is tagged.

EnvironmentTriggerWorkflow
StagingMerge to mainBuild and Deploy Staging
ProductionA vX.Y.Z tag is pushedBuild 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​

  1. In GitHub Actions, run 🏷️ Tag new release on main and pick Patch, Minor or Major.
  2. The workflow creates the next version tag and a GitHub release.
  3. 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.