naro-cli 0.6.0 → 0.7.0

package/README.md

@@ -27,6 +27,27 @@ Values you register are encrypted at rest, and `naro env pull` /
 `naro env list --reveal` can read them back — your account credentials are
 effectively your env credentials.
 
+## Requirements
+
+Next.js **15 or newer**. Next 14 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.
+
+## Build cache
+
+Deploys reuse the dependency and framework caches from your previous build,
+which are stored per project and restored before the install step. The
+archives are zstd-compressed, so caching needs `zstd` on your PATH:
+
+```bash
+brew install zstd     # macOS
+apt install zstd      # Debian/Ubuntu
+```
+
+Without it deploys still work — they just build from scratch every time and
+say so in the build log.
+
 ## Commands
 
 ```text
@@ -41,6 +62,7 @@ naro project inspect               Show the linked project
 naro deploy [--prod]               Build locally and deploy
 naro deployments                   List deployments
 naro inspect <deployment-id>       One deployment + build logs
+naro cancel <deployment-id>        Stop a build that is still running
 
 naro logs                          Runtime logs (production)
 naro logs <deployment-id>          Build logs of a deployment
@@ -54,12 +76,38 @@ naro env pull [.env.local]
 
 naro domains list
 naro domains add www.example.com   Prints the DNS records to create
+naro domains add example.com       Apex: also connects www.example.com and
+                                   redirects the apex to it (--no-www to skip)
+naro domains verify [host]         Re-check DNS now and print what is missing
+naro domains verify --wait         Poll until it goes live (10 min budget)
 naro domains remove www.example.com
 
+naro db enable                     Create the project's database (Cloudflare D1)
+naro db info                       Status, size, table count, limits
+naro db query "select 1"           Run SQL; --file query.sql, or pipe stdin
+naro db push [--dry-run]           Apply pending ./migrations (asks first; --yes in CI)
+naro migration new create_users    Creates migrations/0001_create_users.sql
+naro migration list                Local files vs the d1_migrations ledger
+naro gen types --output src/db.d.ts  TypeScript types for the schema
+
 naro promote <deployment-id>       Publish a build to production
 naro rollback [deployment-id]      Back to the previous production build
 ```
 
+`naro domains list` reads the stored status; `naro domains verify` is the one
+that asks Cloudflare and the DNS again, so it is what turns a stuck "pending"
+into the reason it is stuck. It exits non-zero while a domain is not live —
+with or without `--wait` — so CI can gate on it:
+
+```bash
+naro domains verify www.example.com --wait --json || exit 1
+```
+
+An apex (`example.com`) is added as a pair by default because most registrars
+(Gabia, Whois, Cafe24, GoDaddy) cannot put a CNAME on an apex at all: the CNAME
+goes on `www.example.com` and the apex answers with a 308 redirect to it.
+`--no-www` registers the apex alone.
+
 ## Machine-readable output (CI / AI agents)
 
 Every command supports `--json`: stdout carries exactly one JSON object,
@@ -79,10 +127,10 @@ $ naro deploy --prod --yes --json
 
 Failures carry stable codes (`NOT_LOGGED_IN`, `PROJECT_NOT_LINKED`,
 `FRAMEWORK_UNSUPPORTED`, `BUILD_FAILED`, `DEPLOYMENT_NOT_FOUND`,
-`ENV_NOT_FOUND`, `VALIDATION_FAILED`, `CONFIRMATION_REQUIRED`,
-`CANCELED`, …). A destructive command run non-interactively without
-`--yes` fails with `CONFIRMATION_REQUIRED` instead of silently doing
-nothing:
+`ENV_NOT_FOUND`, `DOMAIN_NOT_FOUND`, `DOMAIN_NOT_READY`,
+`VALIDATION_FAILED`, `CONFIRMATION_REQUIRED`, `CANCELED`, …). A destructive
+command run non-interactively without `--yes` fails with
+`CONFIRMATION_REQUIRED` instead of silently doing nothing:
 
 ```json
 {

package/dist/artifact-types.d.ts

@@ -40,3 +40,18 @@ export interface BuildObserver {
     onStatus?(status: DeploymentStatus): void | Promise<void>;
     onMetadata?(metadata: BuildMetadata): void | Promise<void>;
 }
+/**
+ * Mirrors the persisted deployment strategy record from the internal core
+ * package: what a previous deploy resolved for the project, handed back to
+ * the next build so it can skip the strategy ladder while the record's
+ * fingerprint still matches.
+ */
+export interface DeploymentStrategyRecord {
+    strategy: "vinext-cloudflare" | "opennext-cloudflare" | "split-cloudflare" | "aws-middleware-cloudflare-app" | "opennext-aws";
+    priority: number;
+    nextMajor: number;
+    variant?: string;
+    fingerprint: string;
+    resolvedAt: string;
+    deploymentId: string;
+}