Your Supabase Project Has a 30 October Deadline You Did Not Set
Nothing you ship will trigger it. Four changes landed on the Supabase and Next.js calendars this month, and two of them break running apps on a date somebody else picked.
Most breakage in a production app arrives with a deploy. You change something, something else stops working, and the two events sit close enough together that you find the cause in an afternoon.
Platform deadlines do not work like that. The date is set by somebody else, it lands whether or not you touched the code that quarter, and by the time the error reaches your inbox the change that caused it is a month old and mentioned nowhere in your repository. Four of these landed on the Supabase and Next.js calendars in the last five weeks. Two of them will break a running Lovable app. Here is each one, how to tell in about ten minutes whether it applies to you, and what the fix costs.
30 October 2026: new tables stop reaching the Data API
Supabase is ending the default where a new table in the public schema is automatically exposed to the Data API. The changelog sets out a three-phase rollout: opt-in from 28 April 2026, the default for new projects from 30 May 2026, and enforcement across all projects on 30 October 2026.
This lands hardest on Lovable apps, because the whole Lovable-and-Supabase pattern is that you describe a feature in chat and the platform writes the migration and the client call in the same turn. A call like supabase.from('waitlist_entries') works because the table was exposed the moment it was created. After 30 October, on an existing project, the table exists and the query does not resolve. The failure surfaces in the browser as a data-layer error, not as a migration failure in the Supabase dashboard, which is the wrong place to be looking.
The ten-minute check: list the tables your app queries directly from the client, then open API settings and confirm which schemas are exposed and which tables in them carry grants for anon and authenticated. Supabase documents the exposure path — add the schema under Exposed schemas, then grant on the schema and its tables, routines and sequences, and set default privileges for objects created later. That last part is what stops the next table Lovable writes from landing unreachable.
The fix is configuration, not a migration. The cost is knowing before a user does.
Already live: pgcrypto legacy ciphers stop decrypting
On 25 September Supabase shipped the Postgres 15.19 and 17.11 minor release, bundling five upstream security cycles and 44 CVEs. Four items can require action. One of them is less an upgrade note than a disclosure.
Data encrypted with pgcrypto using cipher-algo=bf, blowfish or cast5 was, in Supabase's own words, effectively stored unencrypted (CVE-2026-14663). After the upgrade, decryption with those ciphers fails by default. Modern ciphers and AES are unaffected. If a prototype ever reached for pgcrypto to protect a token or a field of personal data, this is worth an hour today: the data was not protected, and the code that reads it is now broken as well.
The other three are narrower. ltree indexes need reindexing where the case-folding fixes apply to multibyte or ICU databases, and where values exceed roughly 14,653 labels. btree_gist indexes containing NaN can return incorrect results until reindexed. And attaching non-built-in selectivity estimators to custom operators is now restricted to superusers (CVE-2026-2004), which bites at dump, restore and branching rather than at runtime.
30 September 2026: Next.js patches, if you have already migrated
If you have moved off Vite to Next.js, there are two dates. On 22 September an out-of-band release shipped 16.3.6 and 15.5.26, fixing a critical remote code execution issue in the Node.js ImageResponse implementation in next/og, where improper escaping in Satori's SVG output could reach vulnerable upstream dependencies. Versions >=16.2.0 <16.3.6 are affected; the Edge implementation is not. A scheduled release follows on 30 September as 16.3.7 and 15.5.27, covering nine vulnerabilities — one critical, two high, five medium and one low.
The pattern is worth naming. That is two consecutive critical advisories in the Next.js image path. A Vite SPA serves image files. A Next.js app runs an image service, and an image service is a program that parses input somebody else supplied.
Early 2027: logs become a line item
Also on 25 September, Supabase introduced usage-based pricing for log ingest and query volume, with a grace period through early 2027 and more than 90 percent of projects sitting inside the included limits. Supabase turned down noisy defaults across the fleet at the same time — disabling log_connections removed tens of millions of rows a day — and documents how to tune log_statement and log_min_duration_statement. This is not breakage. But if a prototype was left with verbose logging switched on during a debugging week in the spring, that is now a meter.
The four dates on one page
| Date | What changes | Who it hits | What missing it costs |
|---|---|---|---|
| 30 Oct 2026 | New public tables are no longer auto-exposed to the Data API | Every existing project | A feature ships, the query returns nothing, a user finds it first |
| 25 Sep 2026 (live) | pgcrypto bf, blowfish and cast5 decryption fails after upgrade | Anyone who used the legacy ciphers | Unreadable data, plus the disclosure that it was never really encrypted |
| 25 Sep 2026 (live) | ltree and btree_gist indexes may need reindexing | Projects using those types | Silently wrong results from an index |
| 30 Sep 2026 | Next.js 16.3.7 and 15.5.27 security release | Apps already migrated to Next.js | Nine unpatched vulnerabilities, one of them critical |
| Early 2027 | Supabase log ingest and query volume become metered | Projects left with verbose logging on | A bill line nobody scoped |
Why prototypes get caught by this
Lovable writes your schema, your migrations and your client calls, and it does it well enough that the database stops feeling like something you own. It is yours. The platform's own changelog shows where the line falls: it added a warning when multiple projects share one Supabase instance, because that is a footgun it can detect, and it added a ZIP export of your codebase from Git settings, because at some point the code is yours to run. Neither of those is a calendar. Nobody is going to open a pull request against your repository on 30 October.
That gap is what we get called about. It is rarely a rewrite. It is usually a two-hour audit that ends in a list of four things, two of which turn out not to apply to you.
Getting the four checks run
IdeaFlo has completed 80 jobs on Upwork, turning Lovable and Vite prototypes into applications that survive their own platform's release notes. If you want the four checks above run against your project, the Strategy Audit is $499, one-time, and credited toward any build. If the answer is that the prototype has to become a real application first, the Publishable MVP is $4,999, one-time, and carries the revenue guarantee: first paying customers within 90 days of launch, or full refund.