@devrouter/cli 0.0.60 → 0.0.61
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/dist/devrouter-lifecycle-worker.js +4353 -3818
- package/dist/devrouter.js +963 -551
- package/package.json +2 -1
- package/upgrade-prompts/0.0.61.md +40 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@devrouter/cli",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.61",
|
|
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",
|
|
@@ -49,6 +49,7 @@
|
|
|
49
49
|
"test:package": "./scripts/package-smoke.sh",
|
|
50
50
|
"qualify:lifecycle": "node --import tsx scripts/qualify-lifecycle.ts",
|
|
51
51
|
"qualify:controller": "node --import tsx scripts/qualify-controller.ts",
|
|
52
|
+
"qualify:stop-drift": "node --import tsx scripts/qualify-config-drift-stop.ts",
|
|
52
53
|
"test:process": "bash scripts/test-devrouter-process.sh",
|
|
53
54
|
"check": "biome check .",
|
|
54
55
|
"check:fix": "biome check --write .",
|
|
@@ -0,0 +1,40 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.0.61
|
|
2
|
+
|
|
3
|
+
This patch keeps manual ensure and exec usable after settled operation history
|
|
4
|
+
reaches its bound. Managed Devsy startup records exact stop ownership before
|
|
5
|
+
application readiness on supported local Unix Docker endpoints. With that recorded
|
|
6
|
+
baseline, ordinary stop tolerates changed or missing repository configuration
|
|
7
|
+
without deleting containers or volumes.
|
|
8
|
+
|
|
9
|
+
## Task
|
|
10
|
+
|
|
11
|
+
Install the published patch through the established consumer workflow and update
|
|
12
|
+
`.devrouter.yml` devrouter.version to 0.0.61. No repository schema migration is
|
|
13
|
+
required. Refresh distributed agent guidance through the established workflow.
|
|
14
|
+
|
|
15
|
+
Use canonical ensure, exec and stop for the authorized exact checkout. Stop
|
|
16
|
+
baselines are captured by a qualifying startup; installation alone does not create
|
|
17
|
+
them for older runtimes. Do not fabricate ownership records or replay a failing
|
|
18
|
+
post-create hook to obtain a baseline.
|
|
19
|
+
|
|
20
|
+
## Validation
|
|
21
|
+
|
|
22
|
+
Verify installed version, exact checkout/profile and provider identity. For a
|
|
23
|
+
baseline-backed runtime, verify stop after configuration drift, retained-data
|
|
24
|
+
resume, and final stopped provider state with zero exact routes. Keep existing
|
|
25
|
+
passing evidence only where source, toolchain and relevant environment agree.
|
|
26
|
+
|
|
27
|
+
## Limits
|
|
28
|
+
|
|
29
|
+
Legacy records without a baseline retain the existing configuration-dependent
|
|
30
|
+
stop path. Other recognized Docker transports retain legacy behavior with a
|
|
31
|
+
notice. Invalid or mismatched ownership does not fall back to weaker proof.
|
|
32
|
+
This patch does not repair repository bootstrap/database errors, establish data
|
|
33
|
+
preservation after a destructive hook, prevent every provider replacement, enable
|
|
34
|
+
capacity admission, or provide complete OOM protection or autonomous recovery.
|
|
35
|
+
|
|
36
|
+
## Report
|
|
37
|
+
|
|
38
|
+
Report installed version, exact checkout/profile, whether a stop baseline existed,
|
|
39
|
+
checks performed, retained-data evidence, final provider and route state, and any
|
|
40
|
+
remaining recovery limitation. Distinguish fixture proof from consumer acceptance.
|