@devrouter/cli 0.0.41 → 0.0.43
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.js +309 -239
- package/package.json +2 -1
- package/upgrade-prompts/0.0.42.md +39 -0
- package/upgrade-prompts/0.0.43.md +38 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@devrouter/cli",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.43",
|
|
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",
|
|
@@ -25,6 +25,7 @@
|
|
|
25
25
|
"dependencies": {
|
|
26
26
|
"commander": "^12.1.0",
|
|
27
27
|
"dockerode": "^4.0.9",
|
|
28
|
+
"jsonc-parser": "3.3.1",
|
|
28
29
|
"yaml": "^2.5.1"
|
|
29
30
|
},
|
|
30
31
|
"devDependencies": {
|
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.0.42
|
|
2
|
+
|
|
3
|
+
Devrouter now keeps partially started Devsy workspaces recoverable through the
|
|
4
|
+
canonical lifecycle when the provider returns an error after registering or
|
|
5
|
+
starting the exact checkout.
|
|
6
|
+
|
|
7
|
+
1. Install `@devrouter/cli@0.0.42` on the host and bump `.devrouter.yml` to
|
|
8
|
+
`devrouter.version: 0.0.42`.
|
|
9
|
+
2. Keep using `devrouter ensure`, `devrouter exec`, and `devrouter stop` for
|
|
10
|
+
managed lifecycle operations. No repository schema, Dev Container, runtime,
|
|
11
|
+
route, data, or volume migration is required.
|
|
12
|
+
3. If a cold Devsy start fails after provider mutation, do not remove the
|
|
13
|
+
ignored `.devcontainer/devcontainer.devrouter.json`. Run
|
|
14
|
+
`devrouter stop <checkout>`; devrouter now preserves the generated file when
|
|
15
|
+
exact Devsy absence cannot be proved.
|
|
16
|
+
4. Resolve the reported provider failure, then retry `devrouter ensure` through
|
|
17
|
+
the same canonical lifecycle. Do not switch providers or delete the runtime
|
|
18
|
+
merely to repair a partial start.
|
|
19
|
+
|
|
20
|
+
Verification:
|
|
21
|
+
|
|
22
|
+
- Run `devrouter -V --repo <checkout>` and confirm both the installed CLI and
|
|
23
|
+
local repository report `0.0.42`.
|
|
24
|
+
- Run `devrouter doctor --repo <checkout> --json` and confirm the effective
|
|
25
|
+
workspace runtime and selection source are expected.
|
|
26
|
+
- Run `devrouter ensure <checkout> --json`, then
|
|
27
|
+
`devrouter exec <checkout> -- <representative-command>`.
|
|
28
|
+
- Run `devrouter stop <checkout> --json`, confirm the same exact workspace is
|
|
29
|
+
stopped, and confirm `devrouter ls --json` contains no route for the exact
|
|
30
|
+
checkout.
|
|
31
|
+
|
|
32
|
+
Report template:
|
|
33
|
+
|
|
34
|
+
- CLI/config version: `0.0.42`
|
|
35
|
+
- Effective runtime and source:
|
|
36
|
+
`<devsy/devpod and override/env/path-owner/machine-config/auto-detect/default>`
|
|
37
|
+
- Ensure/exec/route proof: `<passed or details>`
|
|
38
|
+
- Exact non-destructive stop: `<passed or details>`
|
|
39
|
+
- Remaining blockers: `<none or details>`
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.0.43
|
|
2
|
+
|
|
3
|
+
Managed Dev Container startup now requires an explicit lifecycle ordering when
|
|
4
|
+
the source configuration declares `postCreateCommand` and the repository has
|
|
5
|
+
the managed post-start adapter.
|
|
6
|
+
|
|
7
|
+
1. Install `@devrouter/cli@0.0.43` on the host and bump `.devrouter.yml` to
|
|
8
|
+
`devrouter.version: 0.0.43`.
|
|
9
|
+
2. In the source `.devcontainer/devcontainer.json`, set
|
|
10
|
+
`"waitFor": "postCreateCommand"` when it declares `postCreateCommand` and
|
|
11
|
+
uses the managed post-start adapter. `postStartCommand` is also accepted as
|
|
12
|
+
the exact wait point.
|
|
13
|
+
3. Do not edit the generated ignored
|
|
14
|
+
`.devcontainer/devcontainer.devrouter.json`. Managed selective generation
|
|
15
|
+
preserves lifecycle fields and changes only `runServices`; fix the source
|
|
16
|
+
configuration and regenerate it through `devrouter ensure`.
|
|
17
|
+
4. Keep consumer images free of Devrouter packages, helpers, and version pins.
|
|
18
|
+
The host CLI delivers the matching helper at runtime and invokes the
|
|
19
|
+
repository-owned adapter only after the declared lifecycle ordering and
|
|
20
|
+
exact-container proof succeed.
|
|
21
|
+
|
|
22
|
+
Verification:
|
|
23
|
+
|
|
24
|
+
- Run `devrouter repo devcontainer verify --repo <checkout> --json` and confirm
|
|
25
|
+
the source lifecycle ordering is valid.
|
|
26
|
+
- Run `devrouter -V --repo <checkout>` and confirm both the installed CLI and
|
|
27
|
+
local repository report `0.0.43`.
|
|
28
|
+
- Run `devrouter ensure <checkout> --profile <name> --json` when using a
|
|
29
|
+
selective managed profile, then inspect that the generated sibling preserves
|
|
30
|
+
lifecycle fields and changes only `runServices`.
|
|
31
|
+
|
|
32
|
+
Report template:
|
|
33
|
+
|
|
34
|
+
- CLI/config version: `0.0.43`
|
|
35
|
+
- Lifecycle ordering: `<passed or details>`
|
|
36
|
+
- Generated selective configuration: `<passed or details>`
|
|
37
|
+
- Helper-free/version-free image: `<passed or skipped with reason>`
|
|
38
|
+
- Remaining blockers: `<none or details>`
|