| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: b347ccdd-b9a1-4064-9d60-ac410d9a1dca 📥 CommitsReviewing files that changed from the base of the PR and between c44d4a6 and 491cf3a. 📒 Files selected for processing (2)
📝 Walkthrough Summary by CodeRabbit
WalkthroughAPI key validation now uses checkApiKeyFormat, which accepts legacy JWT, recognized sb_, and temporary key formats without throwing. Unknown sb_ subtypes emit a deduplicated warning that excludes the key value. SupabaseClient uses the new helper, and tests cover client creation, warning behavior, temporary-key authentication headers, and omission handling. The migration guide no longer documents exceptions for unrecognized sb_ formats. Sequence Diagram(s)sequenceDiagram
participant SupabaseClient
participant checkApiKeyFormat
participant Console
SupabaseClient->>checkApiKeyFormat: Validate supabaseKey format
checkApiKeyFormat->>Console: Warn once for unknown sb_ subtype
checkApiKeyFormat-->>SupabaseClient: Continue without throwing
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint install timed out. The project may have too many dependencies for the sandbox. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. ❤️ ShareComment @coderabbitai help to get the list of available commands. |
Sorry, something went wrong.
|
@supabase/auth-js
npm i https://pkg.pr.new/@supabase/auth-js@2526
npm i https://pkg.pr.new/@supabase/functions-js@2526
npm i https://pkg.pr.new/@supabase/postgrest-js@2526
npm i https://pkg.pr.new/@supabase/realtime-js@2526
npm i https://pkg.pr.new/@supabase/storage-js@2526
npm i https://pkg.pr.new/@supabase/supabase-js@2526 commit: 491cf3a |
Sorry, something went wrong.
Sorry, something went wrong.
…47960) Adds a contract test that runs `createProjectSupabaseClient()` against the real `@supabase/supabase-js` for each Supabase API key format (temporary, publishable, secret, legacy JWT), asserting that client construction succeeds. Also replaces the placeholder key fixtures in the existing unit tests with realistically shaped ones. Previously the tests mocked the SDK entirely and used keys that don't resemble real formats, so an SDK version that rejects a valid key at construction (as `@supabase/supabase-js` 2.110.4 and 2.110.5 did, reverted in #47945 and fixed in supabase/supabase-js#2526) passed CI unnoticed; with this test, such a regression fails on the dependency bump PR itself. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Tests** * Added coverage confirming project clients work with temporary, publishable, secret, and legacy API key formats. * Updated test scenarios to use realistic temporary API key values. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
This PR updates `@supabase/supabase-js` to v2.110.6. **Source**: supabase-js-stable-release --- ## Release Notes ## v2.110.6 ## 2.110.6 (2026-07-15) ### 🩹 Fixes - **postgrest:** type hinted self-referencing embeds as arrays ([#2520](supabase/supabase-js#2520)) - **realtime:** forward opts to send() in track() ([#2490](supabase/supabase-js#2490)) - **supabase:** warn instead of throw for unrecognized sb_ API key subtypes ([#2526](supabase/supabase-js#2526)) ### ❤️ Thank You - Franco Kaddour @FrancoKaddour - Katerina Skroumpelou @mandarini This PR was created automatically. Co-authored-by: supabase-workflow-trigger[bot] <266661614+supabase-workflow-trigger[bot]@users.noreply.github.com>
This PR updates @supabase/*-js libraries to version 2.110.6. **Source**: supabase-js-stable-release **Changes**: - Updated @supabase/supabase-js to 2.110.6 - Updated @supabase/auth-js to 2.110.6 - Updated @supabase/realtime-js to 2.110.6 - Updated @supabase/postgest-js to 2.110.6 - Refreshed pnpm-lock.yaml --- ## Release Notes ## v2.110.6 ## 2.110.6 (2026-07-15) ### 🩹 Fixes - **postgrest:** type hinted self-referencing embeds as arrays ([#2520](supabase/supabase-js#2520)) - **realtime:** forward opts to send() in track() ([#2490](supabase/supabase-js#2490)) - **supabase:** warn instead of throw for unrecognized sb_ API key subtypes ([#2526](supabase/supabase-js#2526)) ### ❤️ Thank You - Franco Kaddour @FrancoKaddour - Katerina Skroumpelou @mandarini ## v2.110.5 ## 2.110.5 (2026-07-14) ### 🩹 Fixes - **supabase:** avoid edge runtime warning ([#2522](supabase/supabase-js#2522)) ### ❤️ Thank You - Vaibhav @7ttp ## v2.110.4 ## 2.110.4 (2026-07-14) ### 🩹 Fixes - **functions:** stop sending API key in Authorization header for function calls ([#2511](supabase/supabase-js#2511)) - **realtime:** encode broadcast header fields as UTF-8 ([#2516](supabase/supabase-js#2516)) ### ❤️ Thank You - Katerina Skroumpelou @mandarini - Pedro Henrique ## v2.110.3 ## 2.110.3 (2026-07-13) ### 🩹 Fixes - **auth:** preserve pkce verifier ([#2513](supabase/supabase-js#2513)) - **postgrest:** pin tstyche target off floating latest ([#2509](supabase/supabase-js#2509)) ### ❤️ Thank You - Katerina Skroumpelou @mandarini - Vaibhav @7ttp ## v2.110.2 ## 2.110.2 (2026-07-09) ### 🩹 Fixes - **auth:** clear local session on signout failures ([#2504](supabase/supabase-js#2504)) ### ❤️ Thank You - Luc Peng This PR was created automatically. Co-authored-by: supabase-workflow-trigger[bot] <266661614+supabase-workflow-trigger[bot]@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
Description
Relaxes the API key format check in createClient() so that it never throws. Temporary keys (sb_temp_...) are now recognized and accepted silently, and any other unrecognized sb_ key subtype logs a one-time console.warn instead of failing client construction.
What changed?
Why was this change needed?
Versions 2.110.4 and 2.110.5 threw synchronously in the SupabaseClient constructor for any sb_ key that was not sb_publishable_... / sb_secret_... (a future-proofing guard added in #2511). The sb_ key family can grow beyond what any released SDK version knows about, so hard-failing at construction breaks clients that are given valid keys of a newer subtype, such as the temporary sb_temp_... keys. The SDK is not the authority on key validity: with this change, an unrecognized and genuinely invalid key surfaces as an auth error from the server, while an unrecognized but valid key keeps working, with a one-time console warning that an SDK upgrade may be needed.
Screenshots/Examples
Before (2.110.4 and 2.110.5):
After:
Breaking changes
None. This removes a constructor throw, so it strictly widens the set of accepted inputs. Keys that worked before continue to work identically.
Checklist
Additional notes