chore: update @supabase/supabase-js to v2.111.0 - #277
Merged
Conversation
mandarini
approved these changes
Jul 28, 2026
…2.111.0 Since supabase-js 2.111.0 a PKCE flow start writes three storage keys (per-flow verifier slot, flow index, legacy fixed verifier key), each flushed immediately by the server storage adapter. Update the flush count and normalize the random flow id in snapshot cookie names.
mandarini
force-pushed
the
gha/auto-update-supabase-js-v2.111.0
branch
from
July 28, 2026 16:07
eaaee66 to
7280f9a
Compare
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
1 participant
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.
This PR updates
@supabase/supabase-jsto v2.111.0.Source: supabase-js-stable-release
Test update included
supabase-js 2.111.0 (supabase/supabase-js#2569) stores PKCE verifiers in per-flow slots, so a flow start now writes three storage keys instead of one: the per-flow slot, the flow index, and the legacy fixed
-code-verifierkey. Our server storage adapter flushes each of these immediately (by design — slot keys deliberately end in-code-verifier), sosetAllnow fires 3 times per flow start instead of 1.The PKCE verifier test asserted that internal flush count and snapshotted the exact cookies, so we updated it: expect 3
setAllcalls, normalize the random flow id in slot cookie names, and regenerate the snapshots. Test-only change — no source changes needed, the adapter was already prepared in #275.Why this isn't a breaking change in supabase-js: the writes are purely additive — the legacy key is still written with the same format, and
exchangeCodeForSessionwithout a flow id reads it exactly as before. The new slot-only lookup only kicks in when a flow id is explicitly passed or the opt-inexperimental.appendPkceFlowIdToRedirectsflag is enabled.Release Notes
v2.111.0
2.111.0 (2026-07-28)
🚀 Features
❤️ Thank You
This PR was created automatically.