Fixed a panic in project metrics collection that could intermittently stop metrics from being collected under concurrent requests. Each request now gets its own parser instance, ensuring that concurrent metrics requests do not interfere with each other.
All official Supabase client libraries now automatically retry failed database queries due to transient network errors, enhancing reliability without requiring code changes from developers.
Supabase Auth has introduced support for asymmetric key cryptography, providing an additional option to the existing JWT secret for enhanced security.
Supabase will begin including applicable taxes on invoices based on the billing address of organizations, starting from May 1 and completing by June 30. Users are encouraged to verify their billing settings to ensure compliance with tax laws.
Supabase has introduced new email templates to notify users about security-sensitive actions on their accounts, including changes to passwords, emails, phone numbers, and multi-factor authentication settings.
Supabase has introduced the ability to perform inserts, edits, and deletes directly on the Queue table through the table editor interface, enhancing user interaction with the database.
New tables in the public schema will no longer be exposed to the Data API and GraphQL API automatically, requiring explicit opt-in for access. This change will be rolled out progressively starting April 28, 2026.
On March 6, 2026, Supabase introduced a rate limit on recursive and nested Edge Functions calls to improve performance and reduce strain on servers, affecting only a small percentage of projects. This limit applies to outbound fetch calls between Edge Functions within the same project.
The Multigres Kubernetes operator has been made open source, allowing developers to access and contribute to its codebase.
In approximately 3 weeks, the pg_graphql extension will no longer be enabled by default for new Supabase projects and will be disabled for existing projects without GraphQL requests, aligning with a security-first approach. Users will need to manually enable pg_graphql if their applications rely on it.