@devrouter/cli 0.0.73 → 0.0.74
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 +5199 -4964
- package/dist/devrouter.js +753 -518
- package/package.json +1 -1
- package/upgrade-prompts/0.0.74.md +35 -0
package/package.json
CHANGED
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.0.74
|
|
2
|
+
|
|
3
|
+
This patch fixes canonical stop after managed Devsy startup fails before
|
|
4
|
+
registration, including Devsy-only installations without the legacy DevPod CLI.
|
|
5
|
+
It preserves completed startup outcomes and refuses unknown ownership, live
|
|
6
|
+
workers, surviving containers (including stopped containers), and routes.
|
|
7
|
+
No configuration schema, command, or flag migration is required. Successful
|
|
8
|
+
absence proof is reported as `runtimeAbsent: true` in stop JSON.
|
|
9
|
+
|
|
10
|
+
## Task
|
|
11
|
+
|
|
12
|
+
Use the published 0.0.74 CLI. Update `.devrouter.yml` devrouter.version to 0.0.74
|
|
13
|
+
when consumer source changes are authorized; preserve another task's staged
|
|
14
|
+
work. No DevPod installation or runtime-selection change is needed. Refresh
|
|
15
|
+
generated agent guidance only when that repository's owner authorizes it.
|
|
16
|
+
|
|
17
|
+
For an affected exact linked checkout, use canonical `devrouter stop <path>
|
|
18
|
+
--json`. A completed journal alone is not evidence that resources are absent;
|
|
19
|
+
do not edit lifecycle state or delete provider data to bypass a refusal. This
|
|
20
|
+
fix does not recover retained-container identity drift or replace surviving
|
|
21
|
+
resources.
|
|
22
|
+
|
|
23
|
+
## Validation
|
|
24
|
+
|
|
25
|
+
Verify the CLI version and exact checkout ownership. Run the supported stop
|
|
26
|
+
under the checkout owner's recovery authority. Require successful absence proof
|
|
27
|
+
and settled lifecycle state before retrying ensure. Revalidate the original port
|
|
28
|
+
conflict before that retry, then require provider, application and route proof.
|
|
29
|
+
Do not infer consumer recovery from package or regression tests.
|
|
30
|
+
|
|
31
|
+
## Report
|
|
32
|
+
|
|
33
|
+
Report the installed CLI version and release revision, exact checkout, stop
|
|
34
|
+
result, lifecycle state, subsequent ensure and route/application evidence, or
|
|
35
|
+
the precise fail-closed blocker. Confirm source/index and runtime data retention.
|