@devrouter/cli 0.0.54 → 0.0.56
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 +9166 -0
- package/dist/devrouter.js +2759 -3555
- package/package.json +2 -1
- package/upgrade-prompts/0.0.55.md +23 -0
- package/upgrade-prompts/0.0.56.md +52 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@devrouter/cli",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.56",
|
|
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",
|
|
@@ -47,6 +47,7 @@
|
|
|
47
47
|
"dev": "tsx src/cli.ts",
|
|
48
48
|
"test": "vitest run && pnpm test:process",
|
|
49
49
|
"test:package": "./scripts/package-smoke.sh",
|
|
50
|
+
"qualify:lifecycle": "node --import tsx scripts/qualify-lifecycle.ts",
|
|
50
51
|
"test:process": "bash scripts/test-devrouter-process.sh",
|
|
51
52
|
"check": "biome check .",
|
|
52
53
|
"check:fix": "biome check --write .",
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.0.55
|
|
2
|
+
|
|
3
|
+
Managed stop now compares retained mounts independently of the order returned
|
|
4
|
+
by Docker. Exact mount fields and all other retained-runtime guards remain
|
|
5
|
+
mandatory.
|
|
6
|
+
|
|
7
|
+
## Task
|
|
8
|
+
|
|
9
|
+
Install the published patch and update the consumer devrouter.version pin when
|
|
10
|
+
adopting it. No schema migration or generated configuration rewrite is required.
|
|
11
|
+
|
|
12
|
+
## Validation
|
|
13
|
+
|
|
14
|
+
With authorization for an exact runtime, run canonical stop and verify all
|
|
15
|
+
retained containers are stopped with zero exact routes. Preserve the original
|
|
16
|
+
Compose interpolation settings. Use guarded repair only for an eligible
|
|
17
|
+
retained degraded runtime and independently verify application readiness.
|
|
18
|
+
Do not bypass missing state, changed configuration or adapter side-effect gates.
|
|
19
|
+
|
|
20
|
+
## Report
|
|
21
|
+
|
|
22
|
+
Report installed/configured versions, exact checkout/profile, producing command,
|
|
23
|
+
container/route state, application proof and remaining blockers.
|
|
@@ -0,0 +1,52 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.0.56
|
|
2
|
+
|
|
3
|
+
Ordinary managed ensure automatically recovers eligible retained degraded runtimes.
|
|
4
|
+
Durable lifecycle workers preserve stop precedence and proven command outcomes;
|
|
5
|
+
uncertain arbitrary commands are never silently replayed. Current stopped state
|
|
6
|
+
is reported separately from historical transition failures.
|
|
7
|
+
|
|
8
|
+
HTTP proxy apps may declare a readiness path, accepted statuses and content type.
|
|
9
|
+
A failed application check reports application-error and exits nonzero while
|
|
10
|
+
retaining tools and routes for application repair. Unapplied Compose service edits
|
|
11
|
+
no longer prevent exact retained Devsy stop; startup configuration checks remain.
|
|
12
|
+
|
|
13
|
+
## Task
|
|
14
|
+
|
|
15
|
+
Install the published patch and update `.devrouter.yml` devrouter.version to
|
|
16
|
+
0.0.56. Refresh bundled agent guidance through the existing repository workflow.
|
|
17
|
+
No dependency or database migration is required. Adopt application readiness only
|
|
18
|
+
for a bounded read-only endpoint that represents the desired application contract:
|
|
19
|
+
|
|
20
|
+
```yaml
|
|
21
|
+
readiness:
|
|
22
|
+
path: /api/health
|
|
23
|
+
statuses: [200]
|
|
24
|
+
contentType: application/json
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
This field applies to HTTP proxy apps. Existing route-only apps keep their prior
|
|
28
|
+
behavior. Do not treat route reachability as authenticated journey evidence.
|
|
29
|
+
|
|
30
|
+
## Validation
|
|
31
|
+
|
|
32
|
+
On an authorized exact checkout, verify warm ensure, declared application health,
|
|
33
|
+
tooling availability after application failure, and non-destructive stop/resume.
|
|
34
|
+
Confirm retained synthetic records and generated preparation state where relevant.
|
|
35
|
+
After checks, stop the exact runtime and independently verify provider Stopped and
|
|
36
|
+
zero exact routes. Preserve data, caches and other environments.
|
|
37
|
+
|
|
38
|
+
Do not replay unknown commands, remove ownership records, bypass stop fences or
|
|
39
|
+
reset data to force readiness. Ordinary ensure owns supported retained recovery;
|
|
40
|
+
an agent should not need an explicit repair for eligible degraded state.
|
|
41
|
+
|
|
42
|
+
## Limits
|
|
43
|
+
|
|
44
|
+
This release does not activate a machine controller, global capacity admission,
|
|
45
|
+
continuous autonomous recovery or coding-harness enrollment. It does not claim
|
|
46
|
+
complete OOM protection. Unknown ownership and uncertain execution remain explicit.
|
|
47
|
+
|
|
48
|
+
## Report
|
|
49
|
+
|
|
50
|
+
Report installed and configured versions, exact checkout/profile, automatic actions,
|
|
51
|
+
application and tooling proof, warm reuse, retained records, final provider/route
|
|
52
|
+
state and any unsupported cases. Distinguish synthetic tests from live proof.
|