0.22.08
版本发布时间: 2022-09-07 21:35:07
supabase/supabase最新发布版本:1.24.08(2024-09-17 03:37:55)
Launch Week 5 just happened and it was a big one, here is everything we shipped:
Day 1 - Supabase CLI v1 and Admin API Beta
The Supabase CLI is now in v1.0 (including the ability to generate TypeScript types 🎉). We also released the Admin API Beta, a REST API that opens the door to a whole new suite of integrations (Zapier, Terraform, Pulumi, you name it). Full programmatic control of your projects and orgs is on the way.
Day 2 - supabase-js v2 Release Candidate
supabase-js v2 focuses on "quality-of-life" improvements for developers and includes Type Support, new Auth Methods, async Auth overhaul, improvements for Edge Functions, and more. We couldn't have done this without our amazing Community, so thanks a lot to everyone who contributed.
Try it out by running npm i @supabase/supabase-js@rc
Day 3 - Supabase is SOC2 compliant
Our customers can rest assured knowing their information is secure and private 🔒. The blog post explains the process we went through to get there and is very useful for anyone building a SaaS product.
Day 4 - Realtime: Multiplayer Edition
Next level Realtime is here ⚡️. Presence and Broadcast are two key blocks developers can use to build the digital experiences users want. All projects now have access to these features. Try it out in combination with supabase-js v2.
Day 5 - Community Day and One More Thing
We wrapped Launch Week 5 with contributors, partners, and friends and the traditional One More Thing... that was actually SIX more things: Supabase Vault, Auth UI, Dashboard permissions, JSON schema validation, pg_graphql v0.4.0, MFA early-access.
Community Day Video Announcement
Platform Updates
The following changes to the Supabase Platform will take effect from September 11th at 7 pm PDT.
- HTTP API requests to Supabase will automatically be redirected to HTTPS.
- The API Key was passed to Supabase both in the
Authorizationheader and in a separateapiKeyheader. This led to confusion among new users of Supabase who used the API directly. It is no longer required to send the anon key or service key via theapiKeyheader. If you are using Supabase via our client libraries, no change is required from your side.