fix(ci): pin pg_net to extensions schema for migration replay

[glassBead-tc]

Problem

CI on main has been red since ~Jun 5: the Test Suite and Schema Drift Check jobs both die during supabase start with:

ERROR: no schema has been selected to create in (SQLSTATE 3F000)
At statement: CREATE EXTENSION IF NOT EXISTS pg_net

The Supabase CLI applies migrations with an empty search_path. pg_net is a relocatable extension, so a bare CREATE EXTENSION IF NOT EXISTS pg_net (in 20260408033928_add_hub_tables_vectors_pgmq_realtime.sql:7) has no schema to install into and fails. pgmq and pg_cron on the preceding lines have fixed install schemas, so they survive.

Fix

Pin pg_net to the extensions schema — the exact form already used in 20260409232440_remote_schema.sql. No-op where pg_net already exists (prod, staging).

Verification

Verified via CI (local repro blocked by a port conflict with another local Supabase project). The Test Suite job is the signal — it gets past supabase start once this lands.

Note: the Schema Drift Check (supabase db diff --linked) may stay red independently of this fix because production currently has the in-flight tenant-isolation migrations (#353/#354) applied but not yet merged to main; it reconciles once those merge.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
thoughtbox-web-two	Ready	Preview, Comment	Jun 8, 2026 6:03am

[supabase]

This pull request has been ignored for the connected project akjccuoncxlvrrtkvtno due to reaching the limit of concurrent preview branches.
Go to Project Integrations Settings ↗︎ if you wish to update this limit.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[greptile-apps]

Greptile Summary

This PR fixes a broken CI pipeline by adding WITH SCHEMA extensions to the bare CREATE EXTENSION IF NOT EXISTS pg_net statement in an earlier migration file, bringing it into alignment with the form already used in a subsequent migration.

• The Supabase CLI applies migrations under an empty search_path; pg_net is relocatable and has no fallback schema without WITH SCHEMA, causing a 3F000 error during supabase start.
• The fix is a one-line change and is a no-op on environments where pg_net is already installed (production, staging).

Confidence Score: 5/5

Safe to merge. The change is a one-line schema pin with no runtime effect on environments where pg_net is already installed.

The fix is minimal and mechanical: it adds WITH SCHEMA extensions to match the identical form already used in the later migration file. The net.http_post call later in the same migration continues to work because pg_net exposes its HTTP functions through the net schema regardless of the install-time schema target. The change is idempotent on production and staging.

No files require special attention.

Important Files Changed

Filename	Overview
supabase/migrations/20260408033928_add_hub_tables_vectors_pgmq_realtime.sql	Single-line fix: pins pg_net installation to WITH SCHEMA extensions, matching the canonical form already present in the later 20260409232440_remote_schema.sql migration and resolving the empty-search_path failure during CI replay.

Sequence Diagram

sequenceDiagram
    participant CLI as Supabase CLI
    participant DB as PostgreSQL (empty search_path)
    participant ext as extensions schema

    Note over CLI,ext: Migration replay order

    CLI->>DB: 20260408...sql — CREATE EXTENSION pgmq (fixed schema, OK)
    DB-->>CLI: ✓

    CLI->>DB: 20260408...sql — CREATE EXTENSION pg_cron (fixed schema, OK)
    DB-->>CLI: ✓

    Note over CLI,DB: Before fix
    CLI->>DB: CREATE EXTENSION IF NOT EXISTS pg_net
    DB-->>CLI: ERROR 3F000: no schema selected

    Note over CLI,DB: After fix
    CLI->>DB: CREATE EXTENSION IF NOT EXISTS pg_net WITH SCHEMA extensions
    DB->>ext: install pg_net objects into extensions schema
    DB-->>CLI: ✓

    CLI->>DB: 20260409...sql — CREATE EXTENSION pg_net WITH SCHEMA extensions
    DB-->>CLI: ✓ (no-op, already installed)

Loading

_{Reviews (1): Last reviewed commit: "fix(ci): pin pg_net to extensions schema..." | Re-trigger Greptile}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 957d764b60

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Require the remaining CI checks before merge

When this Terraform is applied, main branch protection will require only the Test Suite check, but .github/workflows/ci.yml still defines separate Lint, Type Check, and Schema Drift Check jobs. A PR can therefore merge with type errors, lint failures, or schema drift as long as tests pass, which weakens the CI gate compared with the workflow being run.

Useful? React with 👍 / 👎.

[glassBead-tc]

Superseded by #359, which includes the ci.yml service re-inclusion and validator retirement from this PR, plus the rest of the Test Suite repair. main is green.