Skip to content

docs(deployment): exhibit Git integration disconnected (#34 verification probe) #39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ryandmonk merged 1 commit into from
Aug 4, 2026
Merged

docs(deployment): exhibit Git integration disconnected (#34 verification probe) #39

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions docs/deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,19 +35,19 @@ The workflow authenticates with the repository secret
`CLOUDFLARE_API_TOKEN` (Account → Workers Scripts → Edit, that account
only). Until the secret exists the workflow is inert.

**The previous implicit path (being retired):** the `dspack-studio` Worker
carried a Cloudflare Workers Builds Git integration — repository
**The previous implicit path (disconnected 2026-08-04):** the
`dspack-studio` Worker carried a Cloudflare Workers Builds Git integration — repository
`aestheticfunction/dspack-studio`, production branch `main`, root directory
`/`, build command `pnpm --dir apps/web run build`, deploy command
`npx wrangler deploy`, no path filters, no environment variables — which
rebuilt and redeployed the exhibit on **every** push to `main` (observed
four consecutive times on 2026-08-04, three of them from commits touching
nothing the exhibit consumes; evidence in #34). It must be disabled in the
dashboard: Workers & Pages → `dspack-studio` → Settings → Build →
disconnect the Git repository. Disabling stops future git-triggered builds
only — it does not remove the Worker, its versions, its route, or the
custom domain. The composer Worker has no such integration; its deploys
were always explicit.
six consecutive times on 2026-08-04, four of them from commits touching
nothing the exhibit consumes; evidence in #34). The owner disconnected it
on 2026-08-04 (Workers & Pages → `dspack-studio` → Settings → Build →
disconnect the Git repository); disconnecting stops future git-triggered
builds only — the Worker, its versions, its route, and the custom domain
are unaffected. The composer Worker never had such an integration; its
deploys were always explicit.

The web build is self-sufficient on a clean checkout: `apps/web`'s `build`
script generates the gated contract artifacts first (`packages/contracts/out`
Expand Down
Loading