naro-cli 0.27.0 → 0.28.0

package/README.md

@@ -23,6 +23,18 @@ asks before opening a dotenv file to fill what is missing. Decline and it
 prints the `naro env add` commands instead. With `--yes`, `--json` or outside
 a TTY it never asks — it just lists what is missing and deploys.
 
+An app whose `next.config` sets its own Next.js adapter (`adapterPath`, or
+`experimental.adapterPath`) gets one question on the first deploy: replace it
+with the Naro adapter on Naro's builders (recommended; your repository stays as
+it is) or keep it, in which case Naro builds with vinext only. The answer is
+saved on the project, so the deploy asks once. `--user-adapter replace|keep`
+answers it without a prompt and saves it too; `naro project set --user-adapter
+replace|keep` changes it later. With `--yes`, `--json` or outside a TTY and no
+saved answer, the deploy only warns and builds as before (replace). When the
+saved answer cannot be read, it asks nothing and warns that the setting could
+not be read, since the saved answer may be keep. A local build has no Naro
+adapter either way; the choice matters for Naro's remote builds.
+
 When those names give away a service you are already running, the deploy says
 so instead of leaving you with a list of names. An app that talks to an
 existing Supabase project prints `Supabase — in that project's dashboard:` and
@@ -36,7 +48,7 @@ effectively your env credentials.
 
 ## Requirements
 
-Next.js **15 or newer**. Next 14 and below are not supported — they stop at the
+Next.js **16 or newer**. Next 15 and below are not supported — they stop at the
 version gate right after install with `NEXT_VERSION_UNSUPPORTED`.
 
 Vite, Create React App and plain static sites deploy too.
@@ -65,11 +77,12 @@ naro link | init                   Link this directory to a Naro project
 naro unlink                        Remove the link
 naro projects [--team <slug>]      List projects
 naro project inspect               Show the linked project
-naro usage                         Team usage this month: requests, builds and custom domains against the plan, then by project
+naro usage                         Team usage this month: requests, builds and custom domains against the plan, then by project, then CPU by project and environment
 naro usage --month 2026-09 --team acme  Another UTC month, another team
 
 naro deploy [--prod]               Build locally and deploy
 naro deploy --env qa               Deploy to a named environment (<subdomain>--qa) instead of the preview; not with --prod
+naro deploy --user-adapter keep    Answer the Next.js adapter question up front (replace | keep); see the adapter paragraph above
 naro deployments                   List deployments
 naro inspect <deployment-id>       One deployment + build logs
 naro cancel <deployment-id>        Stop a build that is still running
@@ -884,6 +897,31 @@ An `--update-check` you give replaces the default: without
 
 ## Release notes
 
+### 0.28.0
+
+- Next.js 15 and below are refused up front with `NEXT_VERSION_UNSUPPORTED`
+  (`Naro deploys Next.js 16 or newer.`); a newer major than Naro has a release
+  date for is no longer reported as too old.
+- The OpenNext fallback is gone. Naro's builders try vinext, then the Naro
+  adapter (Next.js 16.2+); local builds try vinext only. An app nothing can
+  build or serve fails with `NO_DEPLOYMENT_STRATEGY`. An unreadable
+  `vinext check` report no longer stops the deploy; the build and the smoke
+  check still decide.
+- `@opennextjs/cloudflare` is no longer a dependency of naro-cli.
+- `naro deploy --user-adapter replace|keep` and `naro project set
+--user-adapter replace|keep` choose what Naro's builders do with an app whose
+  `next.config` sets its own Next.js adapter. `naro deploy` asks once when the
+  project has no saved choice.
+- With `naro project set --vinext off`, Naro's builders (git push,
+  `naro deployments create`) build a Next.js 16.2+ app with the Naro adapter.
+  Local builds (`naro deploy`) have no Naro adapter yet, so a server-rendered
+  Next.js app cannot deploy locally while vinext is off.
+- `naro usage` adds CPU time by project and environment (observed, not
+  billed).
+- naro-mcp 0.27.0 goes out with it: `update_project` and `deploy` take
+  `userAdapter`, `deploy` answers `needsAdapterChoice` when it has to ask, and
+  `get_team_usage` adds `hosting` (CPU time per project and environment).
+
 ### 0.27.0
 
 - `naro supabase` and `naro supabase disconnect` are gone, with the
@@ -921,7 +959,12 @@ browser or your own folder (the capability registry in
 - Projects: `naro project set` (name, subdomain), `naro project check
 <subdomain>`, `naro project access` (`grant`, `revoke`) and `naro project
 delete`, which asks you to type the project's name (`--yes` only with
-  `--project`).
+  `--project`). `naro project set --vinext on|off` switches vinext for the
+  project. It governs Naro's build runner (git and dashboard deploys), where off
+  skips vinext and builds with the Naro adapter (Next.js 16.2 or newer). A local
+  `naro deploy` reads it too but has no Naro adapter, so while it is off
+  `naro deploy` cannot build a server-rendered Next.js app
+  (`NO_DEPLOYMENT_STRATEGY`); static exports (`output: "export"`) still build.
 - The edge: `naro firewall` (`add`, `enable`, `disable`, `remove`), `naro flags`
   (`add`, `on`, `off`, `remove`) and `naro bindings` (`add`, `remove` — removing
   deletes the R2 bucket, KV namespace or D1 database with its data, and asks).
@@ -1895,10 +1938,9 @@ Next.js), `INSTALL_FAILED` (the dependency install), `ARTIFACT_INVALID` (static
 output a deploy cannot take, like a symbolic link), `FRAMEWORK_DETECTION_FAILED`
 (no framework found, or an Angular app without an output path) and
 `BUILD_FAILED` (the app's own build, or a failure that carried no code). A
-Next.js app is built by trying deployment strategies in turn: when the app's
-own `next build` fails, `buildCode` is `BUILD_FAILED`; when its own build did
-not fail but no strategy can ship it, `NO_DEPLOYMENT_STRATEGY`. Either way the message says
-what each strategy failed at.
+Next.js app (16 or newer) is built with vinext. Local builds use vinext only for
+now (no Naro adapter), so an app's own build error there still shows as
+`NO_DEPLOYMENT_STRATEGY`: read the message and the build log.
 
 `--yes` (or `-y`) suppresses every prompt — destructive actions
 (production rollback, promote to production or to an environment, env/domain/environment removal, `naro env import`, turning off an environment's protection, database reset, backend key

package/dist/args.d.ts

@@ -39,6 +39,8 @@ export interface GlobalFlags {
     outputDir?: string | undefined;
     /** `naro project set --vinext on|off`. */
     vinext?: string | undefined;
+    /** `naro project set` and `naro deploy`: --user-adapter replace|keep. */
+    userAdapter?: string | undefined;
     /** `naro storage sign --expires <seconds>`: 1-3600, an hour by default. */
     expires?: string | undefined;
     /** `naro storage sign --download`: the browser saves the file. */

package/dist/artifact-types.d.ts

@@ -2,7 +2,7 @@
 export type DeploymentStatus = "QUEUED" | "CLONING" | "INSTALLING" | "BUILDING" | "DEPLOYING" | "READY" | "FAILED";
 /** Mirrors the artifact file shape from the internal build package. */
 export interface ArtifactFile {
-    /** Module name relative to the OpenNext output root. */
+    /** Module name relative to the build output root. */
     name: string;
     /** Immutable bytes retained after the isolated build workspace is removed. */
     data: Uint8Array;