Skip to content

feat(cli): expose SUPABASE_PUBLISHABLE_KEY in branches get env output#5655

Merged
jgoux merged 1 commit into
supabase:developfrom
mittal-parth:feat/expose-publishable-key
Jun 23, 2026
Merged

feat(cli): expose SUPABASE_PUBLISHABLE_KEY in branches get env output#5655
jgoux merged 1 commit into
supabase:developfrom
mittal-parth:feat/expose-publishable-key

Conversation

@mittal-parth

Copy link
Copy Markdown
Contributor

What is the current behavior?

branches get -o env|json mapped API keys to SUPABASE_<NAME>_KEY by name only. New-format publishable and secret keys both use name default, so the secret overwrote the publishable and SUPABASE_PUBLISHABLE_KEY was never emitted.

What is the new behavior?

This change maps publishable keys named default to SUPABASE_PUBLISHABLE_KEY in the shared ToEnv helper so branches get and projects api-keys return the client key for preview env injection.

Additional context

Closes #5654

branches get -o env|json mapped API keys to SUPABASE_<NAME>_KEY by name only. New-format publishable and secret keys both use name default, so the secret overwrote the publishable and SUPABASE_PUBLISHABLE_KEY was never emitted.

This change maps publishable keys named default to SUPABASE_PUBLISHABLE_KEY in the shared ToEnv helper so branches get and projects api-keys return the client key for preview env injection.
@mittal-parth mittal-parth requested a review from a team as a code owner June 22, 2026 20:28
@jgoux

jgoux commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Thanks for your contribution! 🙏

@jgoux jgoux added this pull request to the merge queue Jun 23, 2026
Merged via the queue into supabase:develop with commit 74c88c8 Jun 23, 2026
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Expose PUBLISHABLE_KEY in supabase branches get

2 participants