anbaric 1.21.0 → 1.21.2

package/README.md

@@ -273,8 +273,8 @@ to the platform automatically. The same applies to `JsonStoreFactory`
 `SqlStoreFactory` (a relational store) from `anbaric-data-store`.
 
 The SQL store is backed by SQLite locally (in-memory by default) and, once
-deployed, by the tenant's PostgreSQL in a schema named after your app — its own,
-isolated from every other app in the tenant. Write portable SQL where you can — the two
+deployed, by the tenant's PostgreSQL in a dedicated `anbaric_app_data` schema
+shared by the tenant's apps. Write portable SQL where you can — the two
 differ in a few places, notably parameter placeholders (`?` for SQLite, `$1`
 for PostgreSQL); see the [`anbaric-data-store`](anbaric-data-store/README.md)
 docs for the full list.

package/docs/api/environment.md

@@ -43,9 +43,7 @@ Used by the store implementations the factories return:
 | --- | --- | --- |
 | `ANBARIC_SQL_FILE` | SQLite | file path to persist to (default `:memory:`) |
 | `ANBARIC_SQL_DATABASE_URL` | PostgreSQL | connection string |
-
-Deployed, the PostgreSQL schema defaults to your **app's name** (each app gets
-its own, isolated schema); pass a schema to the store constructor to override.
+| `ANBARIC_SQL_SCHEMA` | PostgreSQL | schema name (default `anbaric_app_data`) |
 
 ## Platform-injected variables
 
@@ -55,7 +53,7 @@ set or depend on their exact values**:
 | Variable | Meaning |
 | --- | --- |
 | `PORT` | the port your app should listen on |
-| `ANBARIC_APP_ID` | your app's name; scopes your workflows, documents, secrets and SQL schema |
+| `ANBARIC_APP_ID` | your app's name; scopes your workflows, documents and secrets |
 | `ANBARIC_CLOUD_URL` | the platform endpoint the cloud clients call |
 | `ANBARIC_ADMIN_PORT` | the built-in admin/liveness port |
 | `ANBARIC_CONSUMER_PORT` / `ANBARIC_CONSUMER_URL` | job-consumer wiring |

package/docs/features/sql-store.md

@@ -50,10 +50,9 @@ on each. (A future helper may smooth this over; for now, be aware of it.)
 
 - **Local** — SQLite, in-memory by default. Set `ANBARIC_SQL_FILE` to persist to
   a file on disk.
-- **Deployed** — PostgreSQL, in a schema **named after your app** (its own,
-  isolated from every other app in the tenant). The platform provides the
-  connection and the schema; you don't configure either. To use a specific
-  schema instead, pass one to the store constructor.
+- **Deployed** — PostgreSQL, in a dedicated schema (`anbaric_app_data` by
+  default) shared by the tenant's apps and kept apart from the platform's own
+  schemas. The platform provides the connection; you don't configure it.
 
 Selection is by `ANBARIC_SQL_STORE_TYPE` (`sqlite` locally, `cloud`/`postgres`
 deployed) — set by the platform. See [Environment and

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "anbaric",
-  "version": "1.21.0",
+  "version": "1.21.2",
   "description": "Everything needed to write an Anbaric app: state machines, jobs, document and secret stores, local in-memory implementations and the Anbaric Cloud clients",
   "license": "MIT",
   "type": "module",
@@ -15,9 +15,9 @@
     "postpack": "rm -f README.md && ln -s ../README.md README.md"
   },
   "dependencies": {
-    "anbaric-impl-cloud": "^1.21.0",
-    "anbaric-data-store": "^1.21.0",
-    "anbaric-state-machine": "^1.21.0",
-    "anbaric-tsapi": "^1.21.0"
+    "anbaric-impl-cloud": "^1.21.2",
+    "anbaric-data-store": "^1.21.2",
+    "anbaric-state-machine": "^1.21.2",
+    "anbaric-tsapi": "^1.21.2"
   }
 }