CI: auto-deploy the beta-proxy Worker - #273
Merged
Merged
Conversation
beta-proxy/ (the beta.lapwingdata.com reverse proxy) is a separate Worker from the main app, which Cloudflare's connected-repo CI builds — nothing was deploying the proxy, so it had to be pushed by hand. Add deploy-beta-proxy.yml: deploy on BETA pushes that touch beta-proxy/** (and on demand via workflow_dispatch) using cloudflare/wrangler-action, and dry-run validate it on PRs (no secrets, so fork PRs work too). The wrangler version is pinned for reproducible runs since beta-proxy has no committed lockfile. Deploy needs two repo secrets: CLOUDFLARE_API_TOKEN (Edit Workers) and CLOUDFLARE_ACCOUNT_ID. Documented in beta-proxy/README.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TcQYR6dBauo2iSyqt8VkyU
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Coverage SummaryLines: 58.87% (5939/10088) · Statements: 57.93% · Functions: 56.2% · Branches: 53.87% Per-file coverage
|
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
lapwing | c709769 | Commit Preview URL Branch Preview URL |
Jun 21 2026, 08:28 PM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
beta-proxy/reverse-proxy Worker (serves beta.lapwingdata.com →beta-lapwing.perchwerks.workers.dev) is a separate Worker from the main app. Cloudflare's connected-repo CI builds the app, but nothing deployed the proxy — it had to be pushed by hand. This adds a GitHub Actions workflow so it deploys automatically.I verified the worker is already correct and deployable:
wrangler deploy --dry-runpasses (bundles clean, validcustom_domainconfig). The only gap was automation.What this adds
.github/workflows/deploy-beta-proxy.yml:BETAthat touchbeta-proxy/**(and on demand viaworkflow_dispatch), viacloudflare/wrangler-action@v3runningdeploy --config ./wrangler.tomlinbeta-proxy/.beta-proxy/**withwrangler deploy --dry-run— needs no secrets, so it works on fork PRs and catches a brokenwrangler.tomlbefore it reaches BETA.WRANGLER_VERSION) for reproducible runs (beta-proxy has no committed lockfile);concurrencyqueues deploys so two never overlap.Add two repo secrets:
CLOUDFLARE_API_TOKENCLOUDFLARE_ACCOUNT_IDlapwingdata.comzoneAnd the operational prerequisites from
beta-proxy/README.mdstill apply: Cloudflare Access OFF on the upstream preview URL, branch previews enabled onlapwing, and don't hand-create the DNS record (thecustom_domainroute provisions it).Docs
Updated
beta-proxy/README.md(CI section + secrets table) and the deploy note inCLAUDE.md.🤖 Generated with Claude Code
https://claude.ai/code/session_01TcQYR6dBauo2iSyqt8VkyU
Generated by Claude Code