feat(cli): upgrade @supabase/typegen to 0.2.2

[spydon]

Summary

TL;DR: gen types bundles @supabase/typegen@0.2.2, which pins @supabase/postgrest-typegen@0.4.0. TypeScript output gains a ComputedFields key on every table and view, and functions taking a row through a named parameter are typed without the computed fields. Go, Python, Swift and Dart output are unchanged.

Why

postgrest-js leaves computed fields (functions taking the relation's row) out of select('*'), as PostgREST does, and used to infer which Row keys those are from Functions. That inference misses named parameters, which the generator has emitted into Row since CLI 2.118.0, so select('*') on such a relation was typed with keys PostgREST never returns. postgrest-typegen 0.4.0 declares them instead (supabase/sdk#243), and postgrest-js reads the declaration in supabase/supabase-js#2730. Design and measurements in SDK-1986.

What changed

• Bump @supabase/typegen from 0.2.1 to 0.2.2 in apps/cli/package.json; the lockfile moves @supabase/postgrest-typegen from 0.3.1 to 0.4.0 and arktype from 2.2.3 to 2.2.5 (with @ark/schema, @ark/util and arkregex), which 0.4.0 pins exactly.
• pnpm-workspace.yaml: the minimumReleaseAgeExclude entries for the two typegen packages move to the new versions, and the four arktype packages are added. They were published on 2026-09-24 and clear the 7-day window on 2026-10-01, after which their entries can go.

Output change for gen types typescript

channels: {
  Row: { id: number; slug: string | null; get_messages: { ... } | null }
  ComputedFields: "get_messages"        // new; `never` when there are none
  Insert: { ... }
  Update: { ... }
  Relationships: [...]
}
Functions: {
  get_messages: {
    Args: {
      channel_row: Omit<                 // was the plain Row reference
        Database["public"]["Tables"]["channels"]["Row"],
        Database["public"]["Tables"]["channels"]["ComputedFields"]
      >
    }
    ...
  }
}

A function named like a column of the relation it takes is no longer added to that relation's Row; the previous output declared the key twice and did not compile. Unnamed row parameters keep the plain Row reference. Older postgrest-js versions ignore ComputedFields.

Linked issue

SDK-1986 (Linear). No GitHub issue.

• The linked issue is open and carries the open-for-contribution label (or I'm a Supabase maintainer).

Checklist

• The PR title follows Conventional Commits (e.g. fix(cli): …).
• Tests added or updated for the change. No test in this repository asserts on generated TypeScript output; the generator's own tests and parity golden cover it in feat(postgrest-typegen): declare computed fields next to Row and type named row parameters without them sdk#243.
• pnpm types:check passes for apps/cli. gen/types unit tests: 34 pass, types.layers.unit.test.ts does not load locally on my bun (No such built-in module: node:sqlite), unrelated to this change. gen/types integration tests: 94 pass.

[github-actions]

🤖 AI Review

Both independent reviews reported no findings. Reading the changed files and surrounding code confirmed that the dependency versions, lockfile entries, and release-age exclusions are consistent. No concrete issues found; upstream package behavior was not independently verified.

Findings

No issues found.

Stats

Claude findings: 0 · Codex findings: 0 · Confirmed: 0 · Refuted: 0 · Uncertain: 0

---

Models: claude-opus-5-5 + gpt-6.1-sol · Trigger: auto · Workflow run

This review runs once per PR. A maintainer can request another with a /ai-review comment.