diff --git a/.changeset/cli-contract-shoulds.md b/.changeset/cli-contract-shoulds.md deleted file mode 100644 index 2feafa8..0000000 --- a/.changeset/cli-contract-shoulds.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -"@managers/server": minor ---- - -**The CLI contract's remaining `service` and `serve` options (SPEC §1, §3), ported from Paddock ([paddock#996](https://github.com/edspencer/paddock/pull/996)).** What a script can see: - -- **`managers service install --dry-run`** prints the unit it would write (the systemd unit or the launchd plist) on stdout, says where it would go on stderr, and writes nothing — not the unit, not a folder. It works with `--refresh` too, and with `--json` (`{ ok, action, dryRun, unit, contents }`). -- **`service install` refuses to run from a git checkout** (or an `npm link`), exit **1**, unless you add **`--from-checkout`**: a unit that runs a working tree follows every rebuild, branch switch and move of it. A global install is unaffected. The npx refusal now suggests `npm i -g @edspencer/managers` rather than `npm link`, which this refusal would catch. -- **`service install` refuses a port something else holds**, exit **1**, rather than writing a service that can only crash-loop. A Managers on the port (a reinstall) is fine, and so is the unit's own running service. A Paddock on the port counts as something else. -- **`--json` on `service install`, `uninstall`, `start`, `stop` and `restart`**: one document on stdout, `{ ok, action, error?, …the service's status afterwards }` (the same fields as `service status --json`), with every word of prose on stderr. The exit codes don't change; `error` is `busy` for a 75 and `not installed` for a 4. -- **Running `service install` again keeps the installed unit's settings** — its port, host, data dir and verbosity — unless a flag says otherwise (SPEC §1). It used to do that only with `--refresh`, so a plain reinstall over a `--port 9000` service moved it to 7234. -- **`managers serve --quiet` (`-q`)** prints only the first line, `Managers : `. -- **Flags belong to their commands:** `--dry-run` and `--from-checkout` (`service install` only), `--quiet` (`serve` only) and **`--json` on a command that has no JSON document — `serve`, `service logs`, `config eject` — now exit 2**. They used to be accepted and ignored. diff --git a/.changeset/g3-linger-unknown-quiet.md b/.changeset/g3-linger-unknown-quiet.md deleted file mode 100644 index 79a8cb7..0000000 --- a/.changeset/g3-linger-unknown-quiet.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@managers/server": patch ---- - -`managers service install` no longer prints a linger line when `loginctl` can't answer; it prints the `sudo loginctl enable-linger` line only when linger is off, as CLI contract 1.0 (§7) says. `doctor` still reports that case as a skipped check. The copied reference files now name contract 1.0 in their headers. diff --git a/package-lock.json b/package-lock.json index 164a318..7300323 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "managers", - "version": "0.4.0", + "version": "0.5.0", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "managers", - "version": "0.4.0", + "version": "0.5.0", "license": "MIT", "workspaces": [ "packages/*" @@ -11187,7 +11187,7 @@ }, "packages/server": { "name": "@managers/server", - "version": "0.4.0", + "version": "0.5.0", "license": "MIT", "dependencies": { "@fastify/multipart": "^8.3.1", @@ -11758,7 +11758,7 @@ }, "packages/web": { "name": "@managers/web", - "version": "0.4.0", + "version": "0.5.0", "license": "MIT", "dependencies": { "highlight.js": "^11.11.1", diff --git a/package.json b/package.json index 454160f..40d49a5 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "managers", - "version": "0.4.0", + "version": "0.5.0", "private": true, "description": "Managers: scheduled per-project manager agents that track long-running objectives. A fork of Paddock, built on herdctl.", "license": "MIT", diff --git a/packages/server/CHANGELOG.md b/packages/server/CHANGELOG.md index 39e1885..b412be9 100644 --- a/packages/server/CHANGELOG.md +++ b/packages/server/CHANGELOG.md @@ -1,5 +1,23 @@ # @managers/server +## 0.5.0 + +### Minor Changes + +- [#24](https://github.com/edspencer/managers/pull/24) [`db06a62`](https://github.com/edspencer/managers/commit/db06a6275606ab85a96834858998805dca52895e) Thanks [@edspencer](https://github.com/edspencer)! - **The CLI contract's remaining `service` and `serve` options (SPEC §1, §3), ported from Paddock ([paddock#996](https://github.com/edspencer/paddock/pull/996)).** What a script can see: + + - **`managers service install --dry-run`** prints the unit it would write (the systemd unit or the launchd plist) on stdout, says where it would go on stderr, and writes nothing — not the unit, not a folder. It works with `--refresh` too, and with `--json` (`{ ok, action, dryRun, unit, contents }`). + - **`service install` refuses to run from a git checkout** (or an `npm link`), exit **1**, unless you add **`--from-checkout`**: a unit that runs a working tree follows every rebuild, branch switch and move of it. A global install is unaffected. The npx refusal now suggests `npm i -g @edspencer/managers` rather than `npm link`, which this refusal would catch. + - **`service install` refuses a port something else holds**, exit **1**, rather than writing a service that can only crash-loop. A Managers on the port (a reinstall) is fine, and so is the unit's own running service. A Paddock on the port counts as something else. + - **`--json` on `service install`, `uninstall`, `start`, `stop` and `restart`**: one document on stdout, `{ ok, action, error?, …the service's status afterwards }` (the same fields as `service status --json`), with every word of prose on stderr. The exit codes don't change; `error` is `busy` for a 75 and `not installed` for a 4. + - **Running `service install` again keeps the installed unit's settings** — its port, host, data dir and verbosity — unless a flag says otherwise (SPEC §1). It used to do that only with `--refresh`, so a plain reinstall over a `--port 9000` service moved it to 7234. + - **`managers serve --quiet` (`-q`)** prints only the first line, `Managers : `. + - **Flags belong to their commands:** `--dry-run` and `--from-checkout` (`service install` only), `--quiet` (`serve` only) and **`--json` on a command that has no JSON document — `serve`, `service logs`, `config eject` — now exit 2**. They used to be accepted and ignored. + +### Patch Changes + +- [#23](https://github.com/edspencer/managers/pull/23) [`02c7989`](https://github.com/edspencer/managers/commit/02c7989978a7e3d4a48a99fa23f1dd958ae706ce) Thanks [@edspencer](https://github.com/edspencer)! - `managers service install` no longer prints a linger line when `loginctl` can't answer; it prints the `sudo loginctl enable-linger` line only when linger is off, as CLI contract 1.0 (§7) says. `doctor` still reports that case as a skipped check. The copied reference files now name contract 1.0 in their headers. + ## 0.4.0 ### Minor Changes diff --git a/packages/server/package.json b/packages/server/package.json index f633ae4..eb341af 100644 --- a/packages/server/package.json +++ b/packages/server/package.json @@ -1,6 +1,6 @@ { "name": "@managers/server", - "version": "0.4.0", + "version": "0.5.0", "private": true, "description": "Managers backend: Fastify + WebSocket wrapping @herdctl/core FleetManager and a project layer.", "license": "MIT", diff --git a/packages/web/CHANGELOG.md b/packages/web/CHANGELOG.md index 9caf4c0..cc871b8 100644 --- a/packages/web/CHANGELOG.md +++ b/packages/web/CHANGELOG.md @@ -1,5 +1,7 @@ # @managers/web +## 0.5.0 + ## 0.4.0 ### Patch Changes diff --git a/packages/web/package.json b/packages/web/package.json index 609fab0..4e44e0f 100644 --- a/packages/web/package.json +++ b/packages/web/package.json @@ -1,6 +1,6 @@ { "name": "@managers/web", - "version": "0.4.0", + "version": "0.5.0", "private": true, "description": "Managers web SPA (Vite + React + Tailwind).", "license": "MIT",