Skip to content

chore: remove the superseded docker-compose test infra - #314

Merged
Tr00d merged 1 commit into
masterfrom
chore/remove-docker-compose-infra
Aug 7, 2026
Merged

chore: remove the superseded docker-compose test infra#314
Tr00d merged 1 commit into
masterfrom
chore/remove-docker-compose-infra

Conversation

@Tr00d

@Tr00d Tr00d commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Monorepo cleanup — remove docker-compose infra (item 2)

The old docker-compose.yml (postgres 14 / postgrest / gotrue v2.129.1 / storage images) and its .env.sample (AWS keys) predate the move to supabase start, which every package's E2E tier and the CI now use. The docker compose step was already commented out in the workflow.

What changed

  • Removed docker-compose.yml and .env.sample.
  • Updated the Gotrue and Functions README "Testing" sections — they still instructed docker-compose up -d; now supabase start (matching how the tests actually run).

Intentionally kept

  • sdk-compliance.yaml — this is the supabase-js parity tracker (feature → symbol → status), not build cruft. Left in place.
  • release-please config/manifest — belongs with the release-plumbing work, not this cleanup.

No code or build change.

The root docker-compose.yml (old postgres/rest/gotrue/storage images) and its
.env.sample predate the migration to `supabase start`, which is what every package's
E2E tier and CI now use. Remove both, and update the Gotrue and Functions READMEs,
whose "Testing" sections still told contributors to run `docker-compose up -d` -- they
now point at `supabase start`.

sdk-compliance.yaml is intentionally kept: it is the supabase-js parity tracker, not
build cruft.
@Tr00d
Tr00d marked this pull request as ready for review August 7, 2026 10:09
@Tr00d
Tr00d merged commit 2a67632 into master Aug 7, 2026
1 check passed
@Tr00d
Tr00d deleted the chore/remove-docker-compose-infra branch August 7, 2026 10:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant