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 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.