@supabase/supabase-js 2.110.3-canary.0 → 2.110.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@supabase/supabase-js",
-  "version": "2.110.3-canary.0",
+  "version": "2.110.3",
   "description": "Isomorphic Javascript SDK for Supabase",
   "keywords": [
     "javascript",
@@ -59,11 +59,11 @@
     "directory": "packages/core/supabase-js"
   },
   "dependencies": {
-    "@supabase/postgrest-js": "2.110.3-canary.0",
-    "@supabase/realtime-js": "2.110.3-canary.0",
-    "@supabase/auth-js": "2.110.3-canary.0",
-    "@supabase/storage-js": "2.110.3-canary.0",
-    "@supabase/functions-js": "2.110.3-canary.0"
+    "@supabase/auth-js": "2.110.3",
+    "@supabase/functions-js": "2.110.3",
+    "@supabase/postgrest-js": "2.110.3",
+    "@supabase/storage-js": "2.110.3",
+    "@supabase/realtime-js": "2.110.3"
   },
   "devDependencies": {
     "@arethetypeswrong/cli": "^0.18.2",

package/src/SupabaseClient.ts

@@ -165,9 +165,9 @@ export default class SupabaseClient<
    * ```
    *
    * @exampleDescription Custom fetch implementation
-   * `supabase-js` uses the [`cross-fetch`](https://www.npmjs.com/package/cross-fetch) library to make HTTP requests,
+   * `supabase-js` uses the runtime's global `fetch` to make HTTP requests,
    * but an alternative `fetch` implementation can be provided as an option.
-   * This is most useful in environments where `cross-fetch` is not compatible (for instance Cloudflare Workers).
+   * This is useful in environments where the global `fetch` is unavailable or where you want to customize request behavior.
    *
    * @example Custom fetch implementation
    * ```js

package/src/lib/version.ts

@@ -4,4 +4,4 @@
 // - Debugging and support (identifying which version is running)
 // - Telemetry and logging (version reporting in errors/analytics)
 // - Ensuring build artifacts match the published package version
-export const version = '2.110.3-canary.0'
+export const version = '2.110.3'