@devrouter/cli 0.0.68 → 0.0.70

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.68",
+  "version": "0.0.70",
   "description": "Local dev routing CLI with shared Traefik reverse proxy",
   "author": "Roland Schlaefli",
   "homepage": "https://github.com/rschlaefli/devrouter#readme",

package/upgrade-prompts/0.0.69.md

@@ -0,0 +1,41 @@
+# Upgrade to devrouter 0.0.69
+
+This patch release teaches managed `ensure` to refuse — in seconds, with
+attribution — when a consumer-declared fixed published host port is already
+bound by another running container, and adds a read-only doctor check for the
+same drift. It exists because two workspaces collided on one fixed binding and
+the second burned a full provider bootstrap before failing with Docker's raw
+"port is already allocated" and no holder attribution.
+
+## Task
+
+Install the published release and update `.devrouter.yml` devrouter.version to
+0.0.69. No schema migration or configuration change is required. Do not rewrite
+consumer compose files, host ports, or environment defaults to satisfy the
+check: the refusal is intentional, and devrouter never regenerates or offsets
+consumer-declared bindings. When an ensure is refused, resolve the collision on
+the holding side — stop the named workspace with `devrouter stop <path>`, or
+change the consumer's own binding through its declared escape hatch (for
+example its compose interpolation variable) — then run ensure again.
+
+## Validation
+
+On a repository whose managed overlay declares a fixed binding (for example
+`127.0.0.1:${SOME_HOST_PORT:-10003}:10000`), run
+`devrouter doctor --repo <path> --json`: with no live holder,
+`repo.host-port-claims` is `ok`; with another workspace already bound to that
+port it is `error` naming the holding container and owning workspace; with
+Docker unavailable it is `warn` without failing doctor. While the port is
+held, run `devrouter ensure <path> --json`: it must refuse within seconds with
+`hostPortConflicts` populated and a nonzero exit, and no provider bootstrap may
+start. Free or override the port and re-run: ensure completes with routes as
+before. Confirm repositories without fixed published bindings and non-managed
+repositories behave exactly as before.
+
+## Report
+
+Report the tested CLI version, the repository and binding exercised, the
+doctor check level and details before and after, the ensure refusal JSON
+(`hostPortConflicts`) or its absence, the remediation used (stop versus env
+override), and whether any fixed-binding or non-managed regression was
+observed.

package/upgrade-prompts/0.0.70.md

@@ -0,0 +1,23 @@
+# Upgrade to devrouter 0.0.70
+
+This patch release fixes host-port claim reporting so a holder that binds the
+same port on both address families (0.0.0.0 and ::) is reported as one
+conflict instead of duplicates. No schema, configuration, or CLI flag changes.
+
+## Task
+
+Install the published release and update `.devrouter.yml` devrouter.version to
+0.0.70. No configuration change is required.
+
+## Validation
+
+On a repository whose managed overlay declares a fixed published binding that
+a running container holds, run `devrouter doctor --repo <path> --json` and
+confirm `repo.host-port-claims` reports one conflict per distinct binding, not
+one row per address family. `devrouter ensure <path> --json` must return the
+same single `hostPortConflicts` entry.
+
+## Report
+
+Report the tested CLI version, the repository and binding exercised, the
+doctor check details, and whether duplicate conflict rows were observed.