@akirilyuk/supabase-in-memory-server 1.0.0 → 1.0.1

package/README.md

@@ -165,6 +165,18 @@ With **`Prefer: return=representation`**, **PATCH** returns the updated rows in
 
 There is **no** RLS, **no** Realtime WebSocket, **no** Storage, **no** Edge Functions, **no** `/rest/v1/rpc/...`, and **no** full PostgREST operator set (see **TODO** below).
 
+## Publishing (maintainers)
+
+GitHub Actions **Release** workflow (`.github/workflows/release.yml`) runs when you **push a version tag**:
+
+1. Set **`version`** in `package.json` to the release you want (e.g. `1.2.3`).
+2. Commit that change on the default branch (e.g. `main`).
+3. Create and push a tag **`v`** + the same version: `git tag v1.2.3 && git push origin v1.2.3`.
+
+The tag **must** be `vMAJOR.MINOR.PATCH` and match `package.json` exactly (e.g. tag `v1.2.3` ↔ `"version": "1.2.3"`). The workflow runs typecheck, lint, format check, build, and tests, then **`npm publish --access public`** (needed for **scoped** package names) and creates a **GitHub Release** with generated notes.
+
+**Repository secret:** add **`NPM_TOKEN`** in the repo’s **Settings → Secrets and variables → Actions**. Use an [npm access token](https://docs.npmjs.com/creating-and-viewing-access-tokens) with permission to publish this package (granular token for `@scope/package`, or a user token with publish rights).
+
 ## API reference (exports)
 
 The main entry is **`supabase-in-memory-server`** (`dist/index.js`). Notable exports:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@akirilyuk/supabase-in-memory-server",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "In-memory HTTP server mimicking Supabase REST (PostgREST) and Auth (GoTrue) for supabase-js: local testing, e2e, anon/service-role keys, optional CLI, Winston logs",
   "type": "commonjs",
   "main": "./dist/index.js",