fix(ci): pin supabase CLI to 2.105.0 — v2.106.0 breaks local gen types (#298)

* fix(ci): pin supabase CLI to 2.105.0 — v2.106.0 breaks local gen types

supabase CLI v2.106.0 (released 2026-06-11 12:01 UTC) ported `gen types`
to the new TypeScript CLI (supabase/cli#5514); the ported command demands
an access token even for `--local` generation, so the types-drift step
fails with "Access token not provided" on runners without
SUPABASE_ACCESS_TOKEN. Both jobs installed `version: latest` and picked
the release up within minutes (PR #297's run, two minutes after publish).

Pin both setup-cli steps to 2.105.0 (last release before the port) and
bump deliberately once upstream restores token-free local generation.

* fix(ci): de-flake CLI telemetry race in the function-serve step

The verify job's readiness poll resolved API_URL with a third
`supabase status` call that runs concurrently with the backgrounded
`functions serve`. The two CLI processes can race on
~/.supabase/telemetry.json ("error: NotFound: FileSystem.rename"),
crashing status, leaving API_URL empty, and failing the poll with
HTTP 000 for 30s (observed on this PR's first run; main passed the
same script 40 minutes earlier — nondeterministic).

Reuse the URL already captured into .env.local instead of calling
status again, and set DO_NOT_TRACK=1 job-wide — the CLI's documented
telemetry opt-out — so no two CLI invocations contend on the
telemetry file anywhere in the job.

Author: nbhansen

.github/workflows/ci.yml

@@ -15,6 +15,12 @@ jobs:
       # redirects — these are the local-dev values from the config.toml comment.
       SUPABASE_AUTH_SITE_URL: http://127.0.0.1:3000
       SUPABASE_AUTH_REDIRECT_URL: https://127.0.0.1:3000
+      # The CLI's telemetry writer can crash ("NotFound: FileSystem.rename
+      # ~/.supabase/telemetry.json.tmp...") when two invocations run
+      # concurrently — observed 2026-06-11 when `supabase status` raced the
+      # backgrounded `functions serve`. CI needs no telemetry; this is the
+      # CLI's documented opt-out.
+      DO_NOT_TRACK: '1'
     steps:
       - uses: actions/checkout@v6
       - uses: actions/setup-node@v6
@@ -33,7 +39,11 @@ jobs:
       - run: npm run test:functions
       - uses: supabase/setup-cli@v2
         with:
-          version: latest
+          # Pinned: v2.106.0 (2026-06-11) ported `gen types` to the new TS CLI
+          # and broke `--local` generation ("Access token not provided"),
+          # failing the types-drift step. Bump deliberately after verifying
+          # `supabase gen types typescript --local` works without a token.
+          version: 2.105.0
       - run: supabase start
       - name: Regenerate supabase types and fail on drift (#132)
         run: |
@@ -53,7 +63,11 @@ jobs:
           # gateway is up but the function isn't — accepting it here lets the
           # e2e step run against a stalled function and exit non-zero with no
           # useful diagnostics. Require a 4xx (handler response) instead.
-          API_URL="$(supabase status -o json | jq -r '.API_URL')"
+          # Reuse the URL captured into .env.local above — another
+          # `supabase status` here would run concurrently with the
+          # backgrounded serve, the exact telemetry race that emptied
+          # API_URL and failed this step on 2026-06-11.
+          API_URL="$(grep '^SUPABASE_URL=' supabase/functions/.env.local | cut -d= -f2-)"
           ready=0
           for i in {1..30}; do
             STATUS=$(curl -sS --max-time 2 -o /dev/null -w '%{http_code}' \
@@ -81,6 +95,8 @@ jobs:
     env:
       SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}
       PROJECT_REF: ${{ secrets.SUPABASE_PROJECT_REF }}
+      # Same telemetry opt-out as the verify job.
+      DO_NOT_TRACK: '1'
     steps:
       - uses: actions/checkout@v6
       - uses: actions/setup-node@v6
@@ -90,6 +106,7 @@ jobs:
       - run: npm ci
       - uses: supabase/setup-cli@v2
         with:
-          version: latest
+          # Same pin as the verify job — keep both jobs on one CLI version.
+          version: 2.105.0
       - run: supabase link --project-ref "$PROJECT_REF"
       - run: npm run migrations:check-drift