@supabase/functions-js 2.106.2 → 2.107.0-beta.1
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.
- package/AGENTS.md +11 -0
- package/dist/main/version.d.ts +1 -1
- package/dist/main/version.d.ts.map +1 -1
- package/dist/main/version.js +1 -1
- package/dist/main/version.js.map +1 -1
- package/dist/module/version.d.ts +1 -1
- package/dist/module/version.d.ts.map +1 -1
- package/dist/module/version.js +1 -1
- package/dist/module/version.js.map +1 -1
- package/dist/tsconfig.module.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/migrations/README.md +25 -0
- package/package.json +4 -2
- package/src/version.ts +1 -1
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
# Migration notes for `@supabase/functions-js`
|
|
2
|
+
|
|
3
|
+
Each file in this directory describes one migration theme — what changed in `@supabase/functions-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/functions-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/functions-js`:
|
|
10
|
+
|
|
11
|
+
1. Read the migration files in `node_modules/@supabase/functions-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/functions-js` only.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@supabase/functions-js",
|
|
3
|
-
"version": "2.
|
|
3
|
+
"version": "2.107.0-beta.1",
|
|
4
4
|
"description": "JS SDK to interact with Supabase Functions.",
|
|
5
5
|
"main": "dist/main/index.js",
|
|
6
6
|
"module": "dist/module/index.js",
|
|
@@ -18,7 +18,9 @@
|
|
|
18
18
|
"author": "Supabase",
|
|
19
19
|
"files": [
|
|
20
20
|
"dist",
|
|
21
|
-
"src"
|
|
21
|
+
"src",
|
|
22
|
+
"migrations",
|
|
23
|
+
"AGENTS.md"
|
|
22
24
|
],
|
|
23
25
|
"license": "MIT",
|
|
24
26
|
"bugs": {
|
package/src/version.ts
CHANGED
|
@@ -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.
|
|
7
|
+
export const version = '2.107.0-beta.1'
|