@cabane/cli 0.1.0 → 0.1.1

package/README.md

@@ -162,21 +162,4 @@ class) always win over both. Apply a change to an already-running stack with
 - **macOS Gatekeeper** on the unsigned Postgres binaries is a known open question
   (CT453) — documented, not yet solved. If pg fails to exec on first run, clear
   the quarantine xattr and retry.
-- **Before it's published to npm**, install the CLI from a local tarball: `pnpm
---filter @cabane/cli build && cd apps/cli && npm pack`, then `npm i -g
-./cabane-cli-<version>.tgz`. You can also install the _server_ artifact from a
-  local build with `cabane install --from <artifact.tgz>` instead of a token.
-
-## Publishing (maintainers)
-
-The package is publish-ready and source-free — it carries no product source, only
-the bundled supervisor. Verify the tarball first, then publish:
-
-```sh
-pnpm cli:publish:dry   # builds, then `npm publish --dry-run` — lists only dist/ + README
-pnpm cli:publish       # builds (prepublishOnly) + `npm publish --access public`
-```
-
-`cli:publish:dry` should list exactly `dist/cli.js`, `package.json`, and
-`README.md` — no `.ts`. Bump `version` in `apps/cli/package.json` before a real
-publish (npm refuses to overwrite a published version).
+- **Install the _server_ artifact from a local build** with `cabane install --from <artifact.tgz>` instead of a distribution token — handy for an offline or air-gapped install.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cabane/cli",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "type": "module",
   "description": "The cabane CLI — install, supervise (server + embedded Postgres + house bridge), and update a self-hosted Cabane on your own machine. No docker, no repo.",
   "license": "UNLICENSED",