supabase / supabase-flutter / 25015712344

80%

push

github

feat: rename anon key → publishable key, service role key → secret key (#1360)

* feat: rename anon key to publishable key and service role key to secret key

Renames all references to align with Supabase's updated key naming convention:
- `anonKey` parameter → `publishableKey` in Supabase.initialize() and _init()
- `supabaseAnonKey` → `supabasePublishableKey` (internal parameter)
- `ANON_KEY` / `SUPABASE_ANON_KEY` → `PUBLISHABLE_KEY` / `SUPABASE_PUBLISHABLE_KEY` in examples, docs, and infra config
- `service_role` key references in doc comments → `secret` key
- Test variables `anonToken` → `publishableToken` in gotrue tests

JWT role claims (`'role': 'service_role'`) are left unchanged as they are
internal backend values unrelated to the key naming convention.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* fix: deprecate anonKey instead of hard-removing it, revert ANON_KEY env var rename

- Keep anonKey as @Deprecated in Supabase.initialize() so existing callers
  continue to compile; they receive a deprecation warning pointing to publishableKey.
  An assert enforces that at least one of the two is supplied.
- Revert ANON_KEY → PUBLISHABLE_KEY in docker-compose: the storage binary reads
  ANON_KEY by name, renaming it silently breaks the service.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* chore: apply dart format to changed files

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* refactor: rename publishableKey to supabaseKey in public API

The key passed to Supabase.initialize() can be either a publishable key
(anon) or a secret key depending on the use case, so the parameter name
should not imply a specific key type. Aligns with SupabaseClient which
already uses supabaseKey as its positional argument.

- Rename publishableKey parameter -> supabaseKey in Supabase.initialize()
- Update deprecated anonKey message to reference supabaseKey
- Update all call sites in tests, examples, docs, and CHANGELOG
- Reve... (continued)

1 of 1 new or added line in 1 file covered. (100.0%)

3530 of 4390 relevant lines covered (80.41%)

2.86 hits per line