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, which also writes release notes for the finance team and posts them to Slack.

Configuration​

The deploy workflows set every variable, including the Fulfil host, Birdy Bot and the alert channel, so a configuration change is a pull request to the workflow for that environment.

Monitoring​

There are no Cloud Monitoring alert policies for this service, and Sentry isn't configured. Request logs are in Cloud Logging. Workflow failures on the n8n side post to #workflow-alerts.