naro-cli 0.20.0 → 0.22.0

package/README.md

@@ -100,14 +100,16 @@ naro env import .env.qa qa         Upload every variable in a dotenv file to one
                                    stops it before any request, and so does a key a storage binding already uses
                                    when there are over 100 variables; an empty value is uploaded and shown (empty))
 
-naro environments                  List the project's environments: address, branch, protection, and how many the plan allows
+naro environments                  List the project's environments: address, branch, protection, data, and how many the plan allows
 naro environments create qa --branch qa
                                    A QA or staging surface served at <subdomain>--qa; --copy-env preview|production|none
                                    picks where its variables start, --database schema|empty how its database does
 naro environments set qa --no-branch --protection off
                                    Change the branch whose pushes deploy here (--branch <b>, or --no-branch for none)
                                    and who can open it (--protection on|off; off asks first, --yes in CI)
-naro environments delete qa        Delete it with its worker and protection key (asks first; --yes in CI)
+naro environments delete qa        Delete it with its worker, protection key and data (asks first; --yes in CI)
+naro environments provision qa     Make its data (database, backend, Storage), or go on after a stop
+naro db query "select 1" --env qa  Any data command on an environment's data: db, migration, gen, backend, policy, storage, realtime
 
 naro domains list
 naro domains add www.example.com   Prints the CNAME to create; naro connects
@@ -211,6 +213,13 @@ naro storage mv naro://docs/a.pdf naro://docs/old/a.pdf         Inside one bucke
 naro storage rm naro://avatars/u1/old.png [--recursive]   (asks first)
 naro storage rm naro://avatars/u1/ --recursive   Everything under u1/; written u1, an object u1 too
 
+naro realtime [status]             Naro Realtime: on or not, published tables, connections now
+naro realtime enable               Turn Realtime on: the project's hub, bound to its backend
+naro realtime tables [list]        The tables whose Data API writes reach subscribers
+naro realtime tables add <table>…  Publish tables' changes (within about 10 seconds)
+naro realtime tables remove <table>… [--yes]
+                                   Stop publishing tables' changes (asks first)
+
 naro promote <deployment-id> [--to <environment>]   Publish a build to production, or to an environment (0.20.0); says rebuild or reupload first, then asks
 naro rollback [deployment-id]      Back to the previous production build
 ```
@@ -846,6 +855,109 @@ An `--update-check` you give replaces the default: without
 
 ## Release notes
 
+### 0.22.0
+
+0.21.0 went out without this.
+
+- `naro deploy --env <name>` builds with the values the control plane
+  chose for the environment, over the ones it sent (named environments 3d).
+  The control plane saves what the deploy sends for that environment first,
+  so the two differ only where naro sets a name itself: for a project with a
+  Naro backend, an environment's build gets `NARO_URL`,
+  `NEXT_PUBLIC_NARO_URL`, `VITE_NARO_URL`, `PUBLIC_NARO_URL` and the four
+  `…_NARO_ANON_KEY` names set to that environment's own address and anon key.
+  0.21.0 and earlier let a value the deploy sent — typed at the prompt for a
+  missing key, or read from `.env.local` after you agreed — win in the local
+  build, so an environment's app could be built to call the production
+  backend while its worker was given the environment's. `naro deploy --prod`
+  and preview deploys still build with a value sent over the stored one.
+- naro-mcp 0.21.0 goes out with it, with no change of its own: its `deploy` tool sends no env, so the new order does not change what it builds.
+- `--env <name>` on the data commands — `naro db`, `naro migration`,
+  `naro gen types`, `naro backend` (status, keys, auth, users), `naro policy`,
+  `naro storage` and `naro realtime` — acts on that named environment's own
+  database and backend instead of production's (named environments 3e). No
+  `--env`, or `--env production`, is production, which preview shares; this
+  default is not `naro deploy`'s and `naro env pull`'s, which is preview.
+  `--env preview` fails before anything is sent:
+  `--env preview has no data of its own: preview deployments use production's. Drop --env, or name an environment.`,
+  and a value that is no environment's name with
+  `--env must be production or an environment name.` `naro backend enable`
+  and `disable` refuse `--env` (`--env is not an option of naro backend enable: turning the backend on or off applies to every environment.`):
+  every environment's backend follows production's switch. Prompts and result
+  lines name the environment's database (`Reset the qa environment's database?`),
+  and the way back they print carries the `--env` (`naro db restore --bookmark <b> --env qa`).
+  `naro backend --env qa` shows the environment's address and anon key — what a
+  local `.env.local` needs to call that environment's backend.
+  **0.21.0 and earlier ignore `--env` on these commands and act on production**:
+  the control plane cannot tell which CLI sent a request. Update before you
+  use an environment's data.
+- `naro environments` has a `data` column — `provisioning`, `ready`, `error`,
+  or `—` for a project with no Naro database or backend — and prints a stopped
+  run's sentence under the table. `naro environments provision <slug>` makes the
+  environment's data or goes on from where it stopped (`POST …/environments/{id}/provision`).
+  `naro environments delete` now says it removes the environment's data too.
+- `naro deploy --env <name>` no longer asks for `NARO_URL`,
+  `NEXT_PUBLIC_NARO_URL`, `VITE_NARO_URL`, `PUBLIC_NARO_URL` or the four
+  `…_NARO_ANON_KEY` names when the project has a Naro backend: naro sets them
+  for the environment over any value, so a typed one only lost. It reads the
+  project's backend once, and only when one of those names is missing
+  (`▸ naro sets … for qa to its own backend's: not asked for`); a role that
+  cannot read the backend is asked as before.
+
+### 0.21.0
+
+0.20.0 went out on 2026-10-26 without these.
+
+- `naro realtime` turns on Naro Realtime for the project and chooses the
+  tables whose changes reach subscribers (Realtime 3-2d). Five commands:
+  `naro realtime [status]`, `naro realtime enable`,
+  `naro realtime tables [list]`, `naro realtime tables add <table>…` and
+  `naro realtime tables remove <table>… [--yes]`.
+  - `naro realtime` prints `Realtime: on (public channels: off)`, the
+    published tables (`Published tables: messages, gone (dropped)`, or
+    `Published tables: none — naro realtime tables add <table>`) and
+    `Connections now: 12 · channels 30 · presences 8`. When the hub does not
+    answer it says
+    `Connections now: not known — the backend is off or not ready, or the hub did not answer`.
+    Before Realtime is on it prints `Realtime: not enabled` and
+    ``Run `naro realtime enable` to turn it on (the project's backend must be on first).``
+  - `naro realtime enable` needs the backend on, and is safe to run again: it
+    picks up an upload that stopped. It prints
+    `✅ Realtime is on. Publish a table with naro realtime tables add <table>.`
+    and the state. An upload that does not answer within 2 minutes stops
+    with `TIMEOUT`
+    ``Turning Realtime on did not answer within 2 minutes. `naro realtime` shows where it got to, and `naro realtime enable` again picks up where it stopped.``
+  - `naro realtime tables add messages rooms` sends one request a table, in
+    order, and stops at the first refusal (`404 TABLE_NOT_FOUND`
+    `Table nope was not found.`): the tables before it stay published. Each
+    prints `✅ messages now publishes its changes (within about 10 seconds).`
+    and the control plane's warnings as `⚠ <warning>` — for a table with no
+    select policy,
+    `⚠ messages has no select policy: only service-key connections receive its changes.`
+    The command ends with
+    `⚠ Changes made through the Data API are published; writes your app makes with env.DB are not.`
+    once.
+  - `naro realtime tables remove` asks once for all the tables —
+    `Stop publishing messages, rooms? Subscribers stop receiving their changes within about 10 seconds.`
+    — and with `--json` or without a terminal only `--yes` answers it
+    (`CONFIRMATION_REQUIRED`). A table that is not published stops it with
+    `404 TABLE_NOT_PUBLISHED` `Table nope does not publish its changes.`
+  - A table name no URL can carry fails before its request with
+    `INVALID_PATH` `The table name is not valid.`, and a command with no
+    table with `VALIDATION_FAILED` and its usage line.
+- Until Naro Realtime is switched on for the control plane, `naro realtime enable`,
+  `tables add` and `tables remove` answer `503 REALTIME_DISABLED`
+  `Naro Realtime is not enabled on this control plane yet.` (`naro realtime`
+  still prints `Realtime: not enabled`). The tables commands on a project
+  whose Realtime is not on answer `409 REALTIME_NOT_ENABLED`
+  ``Realtime is not enabled for this project. Run `naro realtime enable` first.``
+- There is no command that turns Realtime alone off yet:
+  `naro backend disable` stops it with the rest of the backend.
+- It goes out with naro-js 0.6.0, whose `naro.channel()` is the client side
+  of Realtime (row changes, broadcast and presence, as supabase-js's
+  `channel()`). naro-js 0.6.0 is also the first published version with
+  Storage's `move()` and `copy()` (3-1i).
+
 ### 0.20.0
 
 0.19.1 went out on 2026-10-24 without these.