@specific.dev/spectest 0.56.0 → 0.56.2

package/dist/components/supabase.d.ts

@@ -36,9 +36,12 @@ export interface SupabaseOptions {
     /**
      * Also serve the gateway over **HTTPS** at `https://<hostname>` via the
      * daemon's CA-trusted TLS reverse proxy (in addition to the plain
-     * `http://<name>:8000`). Set this only when the app under test hardcodes a
-     * specific Supabase URL it can't be told to override — otherwise leave it and
-     * point the app at `sb.url`.
+     * `http://<name>:8000`). `sb.url` and `sb.appEnv` then point at the HTTPS
+     * address. Use TLS wherever you can: set this when a browser reaches the
+     * gateway, because a page that is open over `https://` cannot call an
+     * `http://` origin (Chromium blocks the request before it leaves the
+     * browser, and the server logs show nothing). Also set it when the app under
+     * test hardcodes a Supabase URL it cannot be told to override.
      */
     hostname?: string;
     /**

package/dist/mcp-transport.js

@@ -26,6 +26,13 @@
 // at a time and its VM is snapshotted, not disconnected. Add them when a
 // project needs them, not before.
 //
+// It also does not implement the DEPRECATED HTTP+SSE transport
+// (2024-11-05): a long-lived `GET` stream plus a separate POST endpoint
+// named by its first `endpoint` event. A server that speaks only that one
+// answers our `initialize` POST with a `4xx` and this client gives up
+// there. Adding it is a self-contained change — the fallback trigger is
+// that same `4xx` — but nothing needs it yet.
+//
 // Recording lives one layer up. This file is transport only, so `mcp.ts`
 // can record one step per logical operation instead of one per HTTP call.
 import { rawFetch } from "./harness/raw-fetch.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@specific.dev/spectest",
-  "version": "0.56.0",
+  "version": "0.56.2",
   "description": "Spectest SDK for defining test environments in TypeScript.",
   "type": "module",
   "main": "./dist/index.js",

package/src/components/supabase.ts

@@ -239,9 +239,12 @@ export interface SupabaseOptions {
   /**
    * Also serve the gateway over **HTTPS** at `https://<hostname>` via the
    * daemon's CA-trusted TLS reverse proxy (in addition to the plain
-   * `http://<name>:8000`). Set this only when the app under test hardcodes a
-   * specific Supabase URL it can't be told to override — otherwise leave it and
-   * point the app at `sb.url`.
+   * `http://<name>:8000`). `sb.url` and `sb.appEnv` then point at the HTTPS
+   * address. Use TLS wherever you can: set this when a browser reaches the
+   * gateway, because a page that is open over `https://` cannot call an
+   * `http://` origin (Chromium blocks the request before it leaves the
+   * browser, and the server logs show nothing). Also set it when the app under
+   * test hardcodes a Supabase URL it cannot be told to override.
    */
   hostname?: string;
 

package/src/mcp-transport.ts

@@ -26,6 +26,13 @@
 // at a time and its VM is snapshotted, not disconnected. Add them when a
 // project needs them, not before.
 //
+// It also does not implement the DEPRECATED HTTP+SSE transport
+// (2024-11-05): a long-lived `GET` stream plus a separate POST endpoint
+// named by its first `endpoint` event. A server that speaks only that one
+// answers our `initialize` POST with a `4xx` and this client gives up
+// there. Adding it is a self-contained change — the fallback trigger is
+// that same `4xx` — but nothing needs it yet.
+//
 // Recording lives one layer up. This file is transport only, so `mcp.ts`
 // can record one step per logical operation instead of one per HTTP call.