naro-cli 0.25.0 → 0.26.0

package/README.md

@@ -886,6 +886,21 @@ An `--update-check` you give replaces the default: without
 
 ## Release notes
 
+### 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 +1211,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