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.
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.
Rolling backβ
Run Re-Deploy Production (by tag) with the version to restore, for example v1.41.0.
Cloud Run jobsβ
Deploys update the service and its Cloud Run jobs. Merchandising and activation syncs run inside product-sync-job with different arguments, so they pick up each production deploy too.
| Deploy | Jobs updated |
|---|---|
| Production | product-sync-job, collection-sync-job, archive-orphaned-job |
| Staging | back-in-stock-sync-job |