@devrouter/cli 0.3.1 → 0.5.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.3.1",
+  "version": "0.5.0",
   "description": "Local dev routing CLI with shared Traefik reverse proxy",
   "author": "Roland Schlaefli",
   "homepage": "https://github.com/rschlaefli/devrouter#readme",
@@ -51,6 +51,7 @@
     "qualify:capacity": "node --import tsx scripts/qualify-capacity.ts",
     "qualify:controller": "node --import tsx scripts/qualify-controller.ts",
     "qualify:stop-drift": "node --import tsx scripts/qualify-config-drift-stop.ts",
+    "qualify:idle-stop": "node --import tsx scripts/qualify-idle-stop.ts",
     "qualify:harness-journey": "./scripts/qualify-harness-journey.sh",
     "qualify:codex-journey": "DR_JOURNEY_HARNESS=codex ./scripts/qualify-harness-journey.sh",
     "qualify:non-node": "./scripts/qualify-non-node-consumer.sh",

package/upgrade-prompts/0.4.0.md

@@ -0,0 +1,39 @@
+# Upgrade to devrouter 0.4.0
+
+This minor release adds `devrouter env`, which gives host-run tools such as
+Playwright, `psql` or Prisma the endpoints of a checkout's managed runtime.
+
+- `devrouter env [path] [--json]` reports the checkout's routed HTTPS URLs,
+  the routed TLS/SNI and published loopback endpoints of its TCP apps, the
+  workspace token and the mkcert CA path. The JSON report has `version: 1`.
+- `devrouter env [path] -- <command...>` runs a host command without a shell.
+  It exports `DEVROUTER_WORKSPACE`, `DEVROUTER_<APP>_URL`,
+  `DEVROUTER_<APP>_HOST`/`_PORT` (loopback) and
+  `DEVROUTER_<APP>_ROUTED_HOST`/`_ROUTED_PORT`, plus `NODE_EXTRA_CA_CERTS`
+  when it is unset, and returns the command's exit code.
+
+The command only reads state. It never starts or stops a runtime and prints no
+credentials. A loopback endpoint is reported only when exactly one running
+container of this checkout's devcontainer owns the upstream alias and
+publishes the port on a loopback address; otherwise the report names the
+reason. There is no configuration change and no migration.
+
+## Task
+
+Install the published 0.4.0 CLI. No repository change is needed. A repository
+that requires 0.3.x keeps working with 0.4.0. Raise a repository's documented
+minimum devrouter version to 0.4.0 only when consumer source changes are
+authorized and a host script should use `devrouter env` instead of its own
+port discovery.
+
+## Validation
+
+1. Run `devrouter -V` from the consumer checkout. A repository Volta pin can
+   change which install resolves.
+2. With the runtime running, run `devrouter env . --json` and confirm the app
+   URLs and loopback ports match `devrouter status` and `docker port`.
+
+## Report
+
+Report the release revision, the resolved executable with its installed
+version, and any loopback reason other than a running endpoint.

package/upgrade-prompts/0.5.0.md

@@ -0,0 +1,43 @@
+# Upgrade to devrouter 0.5.0
+
+This minor release makes devrouter the owner of idle stop for managed
+devcontainer environments.
+
+- `devrouter workspace idle [--repo <path>] [--idle-for 30m] [--json]` reports
+  each running managed environment as `active`, `idle`, `unknown` or
+  `protected` and changes nothing. `--stop` stops only `idle` environments
+  through the normal `stop` path.
+- `devrouter setup --yes --idle-stop <duration|off>` installs or removes a
+  macOS launchd agent that runs the sweep every five minutes.
+- `devrouter workspace pin [path] [--off]` keeps one environment running
+  regardless of activity.
+- Devsy workspaces now start with an empty `INACTIVITY_TIMEOUT`, which disables
+  Devsy's own idle daemon. `--devsy-inactivity-timeout` and a stored
+  `devsyInactivityTimeout` are deprecated and ignored.
+- `devrouter stop <path>` on a linked worktree devrouter never started now
+  exits 0 with nothing to stop.
+
+Idle stop is opt-in per machine. Nothing stops automatically until a person
+runs `setup --idle-stop`. There is no configuration change and no migration.
+
+## Task
+
+Install the published 0.5.0 CLI. No repository change is needed. A repository
+that requires 0.4.x keeps working with 0.5.0. Bump a repository's
+`devrouter.version` to 0.5.0 only when consumer source changes are authorized.
+Do not run `setup --idle-stop` on a person's machine without their request.
+
+Repositories whose developers rely on database-only sessions should mention
+`devrouter workspace pin .` in their contributor docs, because TCP traffic is
+not observed as activity.
+
+## Validation
+
+1. Run `devrouter -V` from the consumer checkout.
+2. With the runtime running, run `devrouter workspace idle --repo . --json` and
+   confirm the checkout is listed with readable signals.
+
+## Report
+
+Report the release revision, the resolved executable with its installed
+version, and the checkout's idle status and any `unknown` reason.