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 and posts them to #birdy-bot.

To roll back, run Re-Deploy Production (by tag) with an earlier tag.

Configuration​

The deploy workflows don't set any variables. Configuration lives on the Cloud Run service, so a change is made with gcloud run services update in that environment's project. Use --update-secrets for secrets, never --set-secrets, which removes every other secret.

Routing​

Birdy Bot is reached through the platform load balancer, not API Gateway, so Slack and Linear can call it directly. Each route checks its own credentials.

Monitoring​

There are no Cloud Monitoring alert policies for this service, and Sentry isn't installed. Logs are in Cloud Logging. When a Linear triage fails, the bot comments on the issue.