From 7fbe53f025cab0804d17b03b623113c9d3d6eccd Mon Sep 17 00:00:00 2001 From: aarbit Date: Tue, 29 Sep 2026 15:49:44 -0500 Subject: [PATCH] Fix Woodpecker event name: deployment, not deploy MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Caught from the linter warnings on the first real pipeline run (#1) — the production-promotion step's event filter used \`deploy\`, an invalid event name, so it would never have matched Woodpecker's actual deploy-button event (\`deployment\`) and the production step would have silently never run. Staging's own deploy (a push-triggered step) was unaffected and verified working on that same run. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_017DUU6CnxECCDeqDNYJgr5x --- .woodpecker.yml | 6 +++--- deployment-plan.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.woodpecker.yml b/.woodpecker.yml index aeb9b30..59c2163 100644 --- a/.woodpecker.yml +++ b/.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` -# rather than `event: push`. +# deployment event), which is why deploy-production is gated on +# `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: diff --git a/deployment-plan.md b/deployment-plan.md index cbbf59d..df17b16 100644 --- a/deployment-plan.md +++ b/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.