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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@supabase/functions-js",
-  "version": "2.110.3",
+  "version": "2.110.4-canary.0",
   "description": "JS SDK to interact with Supabase Functions.",
   "main": "dist/main/index.js",
   "module": "dist/module/index.js",

package/src/FunctionsClient.ts

@@ -88,7 +88,9 @@ export class FunctionsClient {
    * @category Edge Functions
    *
    * @remarks
-   * - Requires an Authorization header.
+   * - The API key is sent in the `apikey` header. The `Authorization` header is reserved
+   *   for the signed-in user's JWT (or a custom auth token) — when there is no session, a
+   *   new-format API key (`sb_publishable_…` / `sb_secret_…`) is not sent as a Bearer token.
    * - Invoke params generally match the [Fetch API](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API) spec.
    * - When you pass in a body to your function, we automatically attach the Content-Type header for `Blob`, `ArrayBuffer`, `File`, `FormData` and `String`. If it doesn't match any of these types we assume the payload is `json`, serialize it and attach the `Content-Type` header as `application/json`. You can override this behavior by passing in a `Content-Type` header of your own.
    * - Responses are automatically parsed as `json`, `blob` and `form-data` depending on the `Content-Type` header sent by your function. Responses are parsed as `text` by default.

package/src/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'
+export const version = '2.110.4-canary.0'