| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
@supabase/auth-js
npm i https://pkg.pr.new/@supabase/auth-js@2515
npm i https://pkg.pr.new/@supabase/functions-js@2515
npm i https://pkg.pr.new/@supabase/postgrest-js@2515
npm i https://pkg.pr.new/@supabase/realtime-js@2515
npm i https://pkg.pr.new/@supabase/storage-js@2515
npm i https://pkg.pr.new/@supabase/supabase-js@2515 commit: 703c55b |
Sorry, something went wrong.
|
Vlw ai manim 💚 |
Sorry, something went wrong.
|
coverage: 94.167% (+13.7%) from 80.446% — PedroHenrique0713:fix/functions-response-content-type-case into supabase:master |
Sorry, something went wrong.
This PR updates @supabase/*-js libraries to version 2.110.8. **Source**: supabase-js-stable-release **Changes**: - Updated @supabase/supabase-js to 2.110.8 - Updated @supabase/auth-js to 2.110.8 - Updated @supabase/realtime-js to 2.110.8 - Updated @supabase/postgest-js to 2.110.8 - Refreshed pnpm-lock.yaml --- ## Release Notes ## v2.110.8 ## 2.110.8 (2026-07-21) ### 🩹 Fixes - **auth:** downgrade aborted/transient fetch failures from console.error to warn ([#2544](supabase/supabase-js#2544)) - **functions:** clean up cross-signal abort listener on invoke() return ([#2487](supabase/supabase-js#2487)) - **functions:** match response Content-Type case-insensitively ([#2515](supabase/supabase-js#2515)) - **storage:** url-encode object key in CDN purge methods ([#2545](supabase/supabase-js#2545)) - **supabase:** skip Node warning in Deno ([#2541](supabase/supabase-js#2541)) ### ❤️ Thank You - Franco Kaddour @FrancoKaddour - Katerina Skroumpelou @mandarini - Pedro Henrique - Vaibhav @7ttp ## v2.110.7 ## 2.110.7 (2026-07-16) ### 🩹 Fixes - **postgrest:** correct self-reference inference ([#2525](supabase/supabase-js#2525)) - **realtime:** trigger set auth on INITIAL_SESSION event ([#2531](supabase/supabase-js#2531)) - **realtime:** update phoenix to fix presence issue ([#2532](supabase/supabase-js#2532)) ### ❤️ Thank You - Eduardo Gurgel - Filipe Cabaço @filipecabaco - Vaibhav @7ttp 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/supabase-js` to v2.110.8. **Source**: supabase-js-stable-release --- ## Release Notes ## v2.110.8 ## 2.110.8 (2026-07-21) ### 🩹 Fixes - **auth:** downgrade aborted/transient fetch failures from console.error to warn ([#2544](supabase/supabase-js#2544)) - **functions:** clean up cross-signal abort listener on invoke() return ([#2487](supabase/supabase-js#2487)) - **functions:** match response Content-Type case-insensitively ([#2515](supabase/supabase-js#2515)) - **storage:** url-encode object key in CDN purge methods ([#2545](supabase/supabase-js#2545)) - **supabase:** skip Node warning in Deno ([#2541](supabase/supabase-js#2541)) ### ❤️ Thank You - Franco Kaddour @FrancoKaddour - Katerina Skroumpelou @mandarini - Pedro Henrique - Vaibhav @7ttp 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
What changed?
FunctionsClient.invoke() matched the response Content-Type case-sensitively when deciding how to parse the body (responseType === 'application/json', etc.). This normalizes the media type to lower case before matching.
Why was this change needed?
HTTP media types are case-insensitive (RFC 9110 §8.3.1). If an Edge Function responds with Content-Type: Application/JSON (or APPLICATION/JSON), the client currently falls through to the text branch and returns the raw, unparsed string instead of the parsed JSON object.
It's also inconsistent with the request side, which already detects the caller's Content-Type case-insensitively (key.toLowerCase() === 'content-type'); only the response side wasn't.
🔄 Breaking changes
The compared media types are all lower case already, so lower-casing the incoming value only makes matching more tolerant.
📋 Checklist
📝 Additional notes
Added test/spec/response-content-type.spec.ts — a unit test (no relay) using a mocked customFetch asserting that lowercase, mixed-case, and uppercase application/json responses all parse as JSON. Verified locally: the mixed/upper cases fail without the change and pass with it; jest (new spec) → 3 passed, tsc --noEmit → clean, prettier --check → clean.