@supabase/supabase-js 2.106.2 → 2.107.0-beta.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,25 @@
1
+ # Migration notes for `@supabase/supabase-js`
2
+
3
+ Each file in this directory describes one migration theme — what changed in `@supabase/supabase-js`, who is affected, and what callers need to do.
4
+
5
+ Files are shipped with the npm package, so the migration notes you see here are pinned to the version of `@supabase/supabase-js` you have installed. Upgrading the package brings the relevant migration notes along with it.
6
+
7
+ ## How agents should use this directory
8
+
9
+ When helping a developer upgrade `@supabase/supabase-js`:
10
+
11
+ 1. Read the migration files in `node_modules/@supabase/supabase-js/migrations/` for the version they have installed.
12
+ 2. Cross-reference against the version they are upgrading to.
13
+ 3. Apply the migration steps described in each relevant file.
14
+
15
+ ## How humans should use this directory
16
+
17
+ Browse the files for the migration theme you care about. Each file is self-contained and explains its own scope, audience, and steps.
18
+
19
+ ## File naming
20
+
21
+ One file per migration theme, named by topic rather than version (e.g. `<theme>.md`, kebab-case). A single version can ship multiple theme files; a single theme can span multiple versions. Each file documents its own `Since` / `Will require action by` version range internally.
22
+
23
+ ## Cross-cutting migration notes
24
+
25
+ Migrations that span multiple Supabase packages (e.g. Node.js version drops, monorepo restructures) live in [`docs/MIGRATION.md`](../../../../docs/MIGRATION.md) at the repository root, not here. This directory is scoped to `@supabase/supabase-js` only.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@supabase/supabase-js",
3
- "version": "2.106.2",
3
+ "version": "2.107.0-beta.0",
4
4
  "description": "Isomorphic Javascript SDK for Supabase",
5
5
  "keywords": [
6
6
  "javascript",
@@ -13,7 +13,9 @@
13
13
  "author": "Supabase",
14
14
  "files": [
15
15
  "dist",
16
- "src"
16
+ "src",
17
+ "migrations",
18
+ "AGENTS.md"
17
19
  ],
18
20
  "main": "dist/index.cjs",
19
21
  "module": "dist/index.mjs",
@@ -57,11 +59,11 @@
57
59
  "directory": "packages/core/supabase-js"
58
60
  },
59
61
  "dependencies": {
60
- "@supabase/auth-js": "2.106.2",
61
- "@supabase/functions-js": "2.106.2",
62
- "@supabase/realtime-js": "2.106.2",
63
- "@supabase/postgrest-js": "2.106.2",
64
- "@supabase/storage-js": "2.106.2"
62
+ "@supabase/auth-js": "2.107.0-beta.0",
63
+ "@supabase/functions-js": "2.107.0-beta.0",
64
+ "@supabase/realtime-js": "2.107.0-beta.0",
65
+ "@supabase/postgrest-js": "2.107.0-beta.0",
66
+ "@supabase/storage-js": "2.107.0-beta.0"
65
67
  },
66
68
  "devDependencies": {
67
69
  "@arethetypeswrong/cli": "^0.18.2",
package/src/lib/types.ts CHANGED
@@ -182,9 +182,14 @@ export type SupabaseClientOptions<SchemaName> = {
182
182
  */
183
183
  debug?: SupabaseAuthClientOptions['debug']
184
184
  /**
185
- * Provide your own locking mechanism based on the environment. By default no locking is done at this time.
185
+ * Provide your own locking mechanism based on the environment. By default
186
+ * the auth client coordinates refreshes itself and the server resolves
187
+ * cross-tab races. Passing a custom `lock` opts into a legacy path that
188
+ * wraps every auth operation in your supplied lock.
186
189
  *
187
- * @experimental
190
+ * @deprecated Custom locks still work in v2.x for backwards compatibility.
191
+ * The legacy lock path will be removed in v3 — drop this option from your
192
+ * `createClient` options before upgrading.
188
193
  */
189
194
  lock?: SupabaseAuthClientOptions['lock']
190
195
  /**
@@ -200,11 +205,13 @@ export type SupabaseClientOptions<SchemaName> = {
200
205
  */
201
206
  experimental?: SupabaseAuthClientOptions['experimental']
202
207
  /**
203
- * Maximum time in milliseconds to wait when acquiring the auth lock before
204
- * stealing it from the previous holder. See `GoTrueClientOptions.lockAcquireTimeout`
205
- * for full semantics (zero fails immediately, negative waits indefinitely).
208
+ * Maximum time in milliseconds to wait for acquiring the custom lock
209
+ * supplied via `lock`. Only consulted when a custom `lock` is passed.
206
210
  *
207
211
  * @default 5000
212
+ *
213
+ * @deprecated Only used by the legacy lock path. Will be removed in v3
214
+ * along with the `lock` option.
208
215
  */
209
216
  lockAcquireTimeout?: SupabaseAuthClientOptions['lockAcquireTimeout']
210
217
  /**
@@ -4,4 +4,4 @@
4
4
  // - Debugging and support (identifying which version is running)
5
5
  // - Telemetry and logging (version reporting in errors/analytics)
6
6
  // - Ensuring build artifacts match the published package version
7
- export const version = '2.106.2'
7
+ export const version = '2.107.0-beta.0'