feat(functions): bump to 0.1.10 for adding SB_PUBLISHABLE_KEY env for functions - #2
Merged
Merged
Conversation
zakame
changed the title
… functions cf https://github.com/orgs/supabase/discussions/29260 Applying this new key only to the functions deployment for now, but could be used to replace the anonKey on other deployments later - to revisit this upon supabase major upgrade.
anotherainaa
approved these changes
Dec 9, 2025
zakame
force-pushed
the
functions/sb-publishable-key
branch
from
December 9, 2025 07:45
175aa80 to
27fa253
Compare
sanbyk
approved these changes
Dec 9, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
cf https://github.com/orgs/supabase/discussions/29260
Applying this new key only to the functions deployment for now, but could be
used to replace the anonKey on other deployments later - to revisit this upon
supabase major upgrade.
What kind of change does this PR introduce?
Bug fix, feature, docs update, ...
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.