supabase / supabase / 28770359182

75%

push

github

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.

1055 of 1461 branches covered (72.21%)

Branch coverage included in aggregate %.

1576 of 2145 relevant lines covered (73.47%)

249.26 hits per line