naro-cli 0.25.0 → 0.27.0

package/README.md

@@ -102,8 +102,6 @@ naro env remove DATABASE_URL       The production, preview and all values; an en
 naro env pull [.env.local]         Preview's values by default; --env production, or --env qa for an environment
                                    (its own value wins over all; an unknown name fails before anything is written,
                                    and so does a value no dotenv line reads back)
-naro supabase [list]               The project's Supabase links, per target (connect in the dashboard)
-naro supabase disconnect [target]  Remove a target's link, or (no target or all) every link your role may change, with its env vars (asks first)
 naro env import .env.qa qa         Upload every variable in a dotenv file to one target (all by default; asks first,
                                    --yes in CI; an unclosed quote, an invalid key, ASSETS or a value over 5 KB
                                    stops it before any request, and so does a key a storage binding already uses
@@ -886,6 +884,31 @@ An `--update-check` you give replaces the default: without
 
 ## Release notes
 
+### 0.27.0
+
+- `naro supabase` and `naro supabase disconnect` are gone, with the
+  dashboard's Supabase card and its routes. A project reaches its Supabase
+  like anything else: `NEXT_PUBLIC_SUPABASE_URL` and its key with
+  `naro env add`. Variables the card set stay, as your own. Older versions
+  answer `NOT_FOUND` on `naro supabase`.
+- naro-mcp 0.26.0 goes out with it: `list_supabase_links` and
+  `disconnect_supabase` are gone.
+
+### 0.26.0
+
+- `naro dashboard [<capability>]` prints the dashboard URL for what the CLI
+  leaves there on purpose (payments, the GitHub App, Supabase sign-in, saved
+  queries).
+- `naro bindings` is gone, with the dashboard's hosting Storage page and its
+  routes: a project's storage is its Naro backend now — files in Storage,
+  SQL in the database (bound to the app as `env.DB`). Older versions answer
+  `NOT_FOUND` on `naro bindings`, and so does `naro env import` past 100
+  variables, which read the bindings first; this one reads the project only.
+- naro-mcp 0.25.0 goes out with it: `dashboard_link` and server instructions
+  that point at the dashboard for what no tool does; `list_bindings` and
+  `add_binding` are gone. It imports from this release, so publish naro-cli
+  first.
+
 ### 0.25.0
 
 Everything the dashboard does, the CLI now does too, except what needs a
@@ -1196,8 +1219,7 @@ update --verify-jwt <on|off>`, `naro functions invoke` (method, `--data`,
   value (`KEY=`) is uploaded like any other and listed as `(empty)`, so a
   file `naro env pull` wrote for a project holding one imports back. Past
   100 variables, and after you say yes, it reads the project's binding
-  names once (its storage bindings, `ASSETS`, and `DB` on a project with
-  the managed database) and fails `VALIDATION_FAILED`
+  names once (`ASSETS`, and `DB` on a project with the managed database) and fails `VALIDATION_FAILED`
   `<KEY> is already used by a storage binding.` for the first key of the
   file that is one, before the first request; the route refuses such a
   key per request, which left the batches before it saved. Up to 100