$ the-wire · showcase
Studio stops mangling column comments, eval version encoding fixed
By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology
![supabase-releaser[bot]](https://avatars.githubusercontent.com/u/54469796?v=4)
13 people shipped this
farazdagi
@farazdagi
2 cited
jmqd
@jmqd
1 cited
supabase-releaser[bot]
@supabase-releaser[bot]
1 cited
irisfield
@irisfield
1 cited
Ayush Gade
@ayushgade06
1 cited
supabase-evals-releaser
@supabase-evals-releaser
supabase-evals-releaser[bot]
@supabase-evals-releaser[bot]
Rodriguespn
@Rodriguespn
supabase-releaser
@supabase-releaser
supabase-cli-releaser
@supabase-cli-releaser
7ttp
@7ttp
Miranda Limonczenko
@czenko
dav-is
@dav-is
A quiet day across the stack, with two real correctness bugs in Supabase's own code and a Studio data-loss fix that has been silently rewriting user-authored column comments.
fix(studio): prevent column comment data loss from sensitivity marker supabase/supabase
The `[SENSITIVE]` encode/decode helpers matched the marker anywhere in a column comment, so a comment like "Fields marked [SENSITIVE] are PII" was wrongly flagged sensitive and the marker was stripped from the middle of the text on save, even with the toggle off. The fix constrains matching to the marker's real position, so comments survive a round trip through Studio intact.
fix(postgres): correct modern server version encoding supabase/etl
`extract_server_version` encoded PostgreSQL 15.5 as `150500`; since PostgreSQL 10 the documented form is major * 10000 + minor, so `150005` is correct, while pre-10 releases keep the three-component encoding (9.6.3 becomes `90603`). Any comparison against maintenance-release thresholds was being made against the wrong number.
fix(snowflake): validate JSON transitions before schema changes supabase/etl
A source column converted to jsonb could fail after earlier schema changes had already been applied in Snowflake, leaving the destination half-migrated. The fix validates JSON transitions before the schema change goes through, using a repro that alters `payload` to jsonb after dropping a column on the same table.
Log when a table's columns no longer line up with our saved schema supabase/etl
etl matches incoming column values to a saved schema by position, and a partitioned table `ALTER`ed at the parent never reaches etl for each partition, so the saved copy drifts. It now logs when a table's columns no longer line up rather than silently mapping values into the wrong columns.
mcp-server-supabase: v0.16.1 supabase/mcp
mcp-server-supabase v0.16.1 enables the notebook tools by default and adds a `url` field to `get_notebook` and each entry of `list_notebooks`, matching what `create_notebook` already returned. Platforms still only expose the tools when they supply the `notebooks` adapter, which hosted does only with `enableNotebooksV2Api` on.
fix(content api): report GraphQL errors that have no locations supabase/mcp
Elsewhere, the Content API client made `locations` optional in `graphqlErrorSchema` so a Content API error without it reports the actual message instead of a parse failure in `search_docs`; the CLI added migration and seed ordering coverage to its contract suite and found no backend difference; and the Management API OpenAPI specs were resynced into both the CLI and MCP packages.
