.woodpecker.yml

@@ -5,8 +5,8 @@
 # Supabase project — never shares data with production). Production is
 # never touched automatically — promoting to it is a manual "Deploy" button
 # click on a main-branch pipeline run in the Woodpecker UI (Woodpecker's
-# deploy event), which is why deploy-production is gated on `event: deploy`
+# deployment event), which is why deploy-production is gated on
-# rather than `event: push`.
+# `event: deployment` rather than `event: push`.
 #
 # Debian-based node image (not Alpine) for every step: the Supabase CLI's
 # downloaded binary has had musl/Alpine compatibility issues in the past.
@@ -58,7 +58,7 @@ steps:
   - name: deploy-production
     image: node:22-bookworm
     when:
-      - event: deploy
+      - event: deployment
         branch: main
         evaluate: 'CI_PIPELINE_DEPLOY_TARGET == "production"'
     environment:

deployment-plan.md

@@ -121,7 +121,7 @@ revisited and simplified to auto-deploy staging instead.
 **Actual flow**: any push (any branch) runs lint + typecheck, then
 auto-deploys to a shared staging environment — no button needed. Production
 is never touched automatically; promoting to it is a manual **Deploy**
-button click (Woodpecker's built-in deploy event) on a `main`-branch
+button click (Woodpecker's built-in `deployment` event) on a `main`-branch
 pipeline run, typing `production` as the deploy target
 (`$CI_PIPELINE_DEPLOY_TARGET`). Requires **"Allow deployments"** enabled in
 the repo's Woodpecker project settings.