@devrouter/cli 0.4.0 → 0.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@devrouter/cli",
3
- "version": "0.4.0",
3
+ "version": "0.5.1",
4
4
  "description": "Local dev routing CLI with shared Traefik reverse proxy",
5
5
  "author": "Roland Schlaefli",
6
6
  "homepage": "https://github.com/rschlaefli/devrouter#readme",
@@ -51,6 +51,7 @@
51
51
  "qualify:capacity": "node --import tsx scripts/qualify-capacity.ts",
52
52
  "qualify:controller": "node --import tsx scripts/qualify-controller.ts",
53
53
  "qualify:stop-drift": "node --import tsx scripts/qualify-config-drift-stop.ts",
54
+ "qualify:idle-stop": "node --import tsx scripts/qualify-idle-stop.ts",
54
55
  "qualify:harness-journey": "./scripts/qualify-harness-journey.sh",
55
56
  "qualify:codex-journey": "DR_JOURNEY_HARNESS=codex ./scripts/qualify-harness-journey.sh",
56
57
  "qualify:non-node": "./scripts/qualify-non-node-consumer.sh",
@@ -0,0 +1,43 @@
1
+ # Upgrade to devrouter 0.5.0
2
+
3
+ This minor release makes devrouter the owner of idle stop for managed
4
+ devcontainer environments.
5
+
6
+ - `devrouter workspace idle [--repo <path>] [--idle-for 30m] [--json]` reports
7
+ each running managed environment as `active`, `idle`, `unknown` or
8
+ `protected` and changes nothing. `--stop` stops only `idle` environments
9
+ through the normal `stop` path.
10
+ - `devrouter setup --yes --idle-stop <duration|off>` installs or removes a
11
+ macOS launchd agent that runs the sweep every five minutes.
12
+ - `devrouter workspace pin [path] [--off]` keeps one environment running
13
+ regardless of activity.
14
+ - Devsy workspaces now start with an empty `INACTIVITY_TIMEOUT`, which disables
15
+ Devsy's own idle daemon. `--devsy-inactivity-timeout` and a stored
16
+ `devsyInactivityTimeout` are deprecated and ignored.
17
+ - `devrouter stop <path>` on a linked worktree devrouter never started now
18
+ exits 0 with nothing to stop.
19
+
20
+ Idle stop is opt-in per machine. Nothing stops automatically until a person
21
+ runs `setup --idle-stop`. There is no configuration change and no migration.
22
+
23
+ ## Task
24
+
25
+ Install the published 0.5.0 CLI. No repository change is needed. A repository
26
+ that requires 0.4.x keeps working with 0.5.0. Bump a repository's
27
+ `devrouter.version` to 0.5.0 only when consumer source changes are authorized.
28
+ Do not run `setup --idle-stop` on a person's machine without their request.
29
+
30
+ Repositories whose developers rely on database-only sessions should mention
31
+ `devrouter workspace pin .` in their contributor docs, because TCP traffic is
32
+ not observed as activity.
33
+
34
+ ## Validation
35
+
36
+ 1. Run `devrouter -V` from the consumer checkout.
37
+ 2. With the runtime running, run `devrouter workspace idle --repo . --json` and
38
+ confirm the checkout is listed with readable signals.
39
+
40
+ ## Report
41
+
42
+ Report the release revision, the resolved executable with its installed
43
+ version, and the checkout's idle status and any `unknown` reason.
@@ -0,0 +1,27 @@
1
+ # Upgrade to devrouter 0.5.1
2
+
3
+ This patch release fixes lifecycle commands that failed with
4
+ `docker inspect failed: error: no such object: <id>` when any container on the
5
+ machine was removed while devrouter was listing containers, for example while
6
+ another checkout's stack was being recreated. `ensure`, `exec`, `stop`,
7
+ `status` and `workspace idle` now treat such a vanished container as absent.
8
+ Other inspect errors still fail. There is no configuration change and no
9
+ migration.
10
+
11
+ ## Task
12
+
13
+ Install the published 0.5.1 CLI. No repository change is needed. Bump a
14
+ repository's `devrouter.version` to 0.5.1 only when consumer source changes are
15
+ authorized. A machine that uses the idle-stop agent needs no setup rerun when
16
+ devrouter is installed through Volta, because the agent's entry path does not
17
+ change between versions.
18
+
19
+ ## Validation
20
+
21
+ 1. Run `devrouter -V` from the consumer checkout.
22
+ 2. Run `devrouter workspace idle --json` and confirm it completes.
23
+
24
+ ## Report
25
+
26
+ Report the release revision and the resolved executable with its installed
27
+ version.