layero 0.8.4 → 0.8.6

package/README.md

@@ -80,7 +80,7 @@ Run `layero <cmd> --help` for full options.
 - `--name <name>` — project name (only on first deploy).
 - `--project <id_or_slug>` — deploy into an existing project, ignoring
   `./.layero/project.json` (useful for CI).
-- `--prod` — deploy to the project's apex hostname (replaces production). Without it, deploys go to a preview pseudo-branch and never touch prod.
+- `--prod` — target the production environment of a repository-linked project. **Redundant for CLI projects**: a project created by `layero deploy` auto-promotes to its apex on every deploy, so a plain `deploy` already replaces the live site. Use `--branch <name>` when you want a publish that leaves the live address alone.
 - `--branch <name>` — deploy to a specific branch's environment.
 - `--org <slug>` — Layero organization for first-time project creation.
 - `--yes` / `-y` — non-interactive mode.
@@ -151,6 +151,42 @@ faster deploys, no surprises from the platform's package-manager defaults.
 
 Override anything by editing `.layero/project.json` after the first `layero init`.
 
+## In CI
+
+`layero login` opens a browser — there isn't one on a runner, so a pipeline
+authenticates with a long-lived token instead. Create it at
+[app.layero.ru/settings/cli](https://app.layero.ru/settings/cli) and pass it
+through the environment:
+
+```bash
+LAYERO_TOKEN=... npx layero@latest deploy --prod --yes
+```
+
+`LAYERO_TOKEN` is read **before** `~/.layero/config.json`, deliberately: on a
+developer machine that is already signed in to a different account, the
+opposite order would silently deploy to the wrong place. `--yes` skips the
+confirmation prompt that would otherwise wait forever with nobody to answer it.
+
+The token is account-scoped, like a login session, so create a separate one per
+repository — then a leak is contained to that repository. Revoke on the same
+page; running builds start failing immediately.
+
+On GitHub Actions there is an official action that wraps the above:
+
+```yaml
+      - uses: LayeroInfra/deploy-action@v1
+        with:
+          token: ${{ secrets.LAYERO_TOKEN }}
+          prod: true
+```
+
+Note that if the repository is already linked to a Layero project, a push
+builds it automatically — a pipeline would only duplicate that work. Reach for
+CI when the build itself needs secrets or private dependencies the platform
+does not have, then ship the result with `prebuilt: dist`.
+
+Full guide: <https://docs.layero.ru/cli/github-actions>
+
 ## Agent / JSON mode
 
 `layero` auto-switches to non-interactive + structured-output mode when any of these is true:
@@ -181,10 +217,20 @@ Event types emitted on stdout:
 {"event":"error","code":"…","next_action":"…","message":"…"}
 ```
 
-On `ready`, `url` is the **live public site** (the apex — CLI uploads
-auto-promote to it), `preview_url` is reachable immediately while the apex CDN
-edge warms (`edge_ready=false`), and `dashboard_url` is the management page (not
-the site). Not logged in? `deploy` starts the device-flow itself (`auth_required`).
+On `ready`, `url` is the **live public site** — reachable the moment the event
+arrives. Show it as-is and never rebuild the hostname from a template: project
+addresses live in the `layero.app` zone, organizations that have not migrated
+yet still use the older `<org>-<project>.layero.ru` scheme, and a guessed host
+will be wrong for one of the two. `dashboard_url` is the management page, not
+the site.
+
+`preview_url`, `edge_ready` and `edge_eta_seconds` are legacy fields from the
+era when user sites sat behind a CDN that needed warming. They no longer do —
+sites are served straight from the platform edge. `preview_url` is `null` for
+projects in the `layero.app` zone. **Do not gate on `edge_ready`**: waiting for
+it means waiting for something that will not arrive.
+
+Not logged in? `deploy` starts the device-flow itself (`auth_required`).
 
 Errors carry a stable `code` (e.g. `not_logged_in`, `invalid_type`,
 `project_not_found`, `cli_deploys_disabled`) and a `next_action` hint so

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "layero",
-  "version": "0.8.4",
+  "version": "0.8.6",
   "description": "Layero CLI — publish a local site with one command. No git, no GitHub, agent-friendly (Cursor, Claude Code).",
   "license": "MIT",
   "type": "module",
@@ -13,14 +13,23 @@
     "deploy",
     "deployment",
     "hosting",
+    "static-hosting",
     "cdn",
     "cli",
     "static-site",
     "spa",
     "ssr",
+    "vite",
+    "nextjs",
+    "astro",
+    "sveltekit",
     "ai-agents",
     "cursor",
-    "claude-code"
+    "claude-code",
+    "mcp",
+    "vercel-alternative",
+    "netlify-alternative",
+    "russia"
   ],
   "engines": {
     "node": ">=20"
@@ -52,5 +61,9 @@
     "@types/node": "^20.14.10",
     "typescript": "^5.5.4",
     "vitest": "^4.1.7"
+  },
+  "author": {
+    "name": "Layero",
+    "url": "https://layero.ru"
   }
 }