Files
supabase/apps/studio/components/interfaces
Wen Bo Xie 5c3d250140 docs: clarify that creating new API keys does not disable legacy keys (#47395)
Creating publishable and secret keys adds them alongside the existing
anon and service_role keys without affecting them. Make this explicit in
two places so users don't assume their legacy keys are revoked:

- Add an Admonition note to the API keys guide explaining both key types
work simultaneously and legacy keys must be disabled in a separate step.
- Update the "Create new API keys" dialog in Studio to reassure users
that their existing anon and service_role keys remain valid.
2026-07-06 05:39:59 +00:00
..
2026-07-02 17:03:08 +02:00
2026-07-01 08:24:17 -06:00
2026-07-03 15:00:43 +10:00
2026-07-03 15:00:43 +10:00
2026-07-03 15:00:43 +10:00
2026-07-03 15:00:43 +10:00
2026-07-03 15:00:43 +10:00
2026-07-03 15:00:43 +10:00
2026-07-03 15:00:43 +10:00