Skip to content

Commit 1f7150a

Browse files
committed
ci: run d1 migrations during cloudflare deploy
1 parent 674da64 commit 1f7150a

2 files changed

Lines changed: 4 additions & 7 deletions

File tree

.github/workflows/deploy-cloudflare.yml

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -128,9 +128,7 @@ jobs:
128128
run: pnpm install --frozen-lockfile
129129

130130
- name: Deploy relay
131-
run: |
132-
make relay-deploy-dry-run
133-
pnpm --dir relay exec wrangler deploy --domain "$RELAY_DOMAIN"
131+
run: make relay-deploy
134132

135133
deploy-workbench:
136134
name: Deploy Workbench Pages

README.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -162,10 +162,9 @@ CLOUDFLARE_API_TOKEN
162162
CLOUDFLARE_ACCOUNT_ID
163163
```
164164

165-
The Cloudflare token must be able to deploy Workers and Cloudflare Pages. D1
166-
migrations still run through `make relay-deploy`; enable D1 write on the deploy
167-
token before switching the GitHub Actions relay step to that target. The
168-
workflow uses these defaults:
165+
The Cloudflare token must be able to deploy Workers and Cloudflare Pages, and
166+
it must include D1 write access because the relay deployment applies remote D1
167+
migrations before publishing the Worker. The workflow uses these defaults:
169168

170169
```text
171170
ACP_RUNTIME_REPO_URL=https://github.com/saaskit-dev/acp-runtime.git

0 commit comments

Comments
 (0)