Repository navigation
fix(cli): bump @supabase/typegen to 0.3.3 - #7585
Merged
Merged
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
🤖 AI Review
Both independent reviews reported no findings. Code inspection confirms the dependency versions, lockfile entries, and release-age exclusions are consistent. No fundamental conflict with the listed next-branch work is evident. Upstream package behavior could not be verified from the checked-out files.
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.
Contributor
CLI benchmark (Lightweight Commands): no changes foundCommit
API calls: unchanged for all 8 commands. Binary size: 135.0 MB, up 12.0 KB from 135.0 MB. Details: timing ranges, API calls per command, slowest phasesTiming ranges
API calls per command
Slowest phasesNo command moved beyond noise, so there are no phase deltas. Comment |
jgoux
requested changes
Nov 12, 2026
jgoux
left a comment
jgoux
left a comment
Contributor
There was a problem hiding this comment.
The bump makes supabase gen types fail outright against PostgreSQL 13 databases; details inline. The lockfile and minimumReleaseAgeExclude entries are otherwise consistent with the new versions.
jgoux
self-requested a review
November 12, 2026 10:53
jgoux
approved these changes
Nov 12, 2026
spydon
added a commit
to supabase/sdk
that referenced
this pull request
Nov 12, 2026
The Supabase CLI is dropping PostgreSQL 13, which makes 14 the oldest version `introspect()` has to support. On 14, view column nullability and `RETURNS TABLE` column nullability inferred nothing: PostgreSQL 14 writes range table entries as `RTE` in its node trees, where 15 and later write `RANGETBLENTRY`, and the walk only accepted the latter. Every view column and every `RETURNS TABLE` column on a PostgreSQL 14 database was therefore generated as nullable. The walk now accepts both names, and on 14 the full test fixture produces exactly the same output as on 15. To keep the minimum supported version working, the parity test now runs on PostgreSQL 14 (`MINIMUM_POSTGRES_VERSION`) as well as 15, against the same golden files. A query that reads a catalog column added after 14, or any other difference in what 14 produces, fails every pull request. The view and `RETURNS TABLE` nullability suites include 14 too. Without the fix, 11 tests fail on 14; with it, the full suite passes. The README has a new "Supported PostgreSQL versions" section that names the minimum and where it is enforced. Generated output on PostgreSQL 15 and later is unchanged. Context: supabase/cli#7585 (comment) found that 0.8.0 fails on PostgreSQL 13, because it reads `pg_proc.prosqlbody`, which exists from 14. With 13 no longer supported, that query stays as it is.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps
@supabase/typegento 0.3.3, which pulls in@supabase/postgrest-typegen0.8.0. That release infers column nullability for functions thatRETURNS TABLE, sosupabase gen typesemits more accurate return types for those functions.The
minimumReleaseAgeExcludeentries inpnpm-workspace.yamlmove to the new versions.Release notes: typegen 0.3.3, postgrest-typegen 0.8.0.