@devrouter/cli 0.0.39 → 0.0.41
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/README.md +5 -3
- package/dist/devrouter.js +1023 -301
- package/package.json +1 -1
- package/upgrade-prompts/0.0.40.md +34 -0
- package/upgrade-prompts/0.0.41.md +43 -0
package/package.json
CHANGED
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.0.40
|
|
2
|
+
|
|
3
|
+
Devrouter now keeps a managed DevPod stoppable when its first profile
|
|
4
|
+
transition fails. The ignored generated Dev Container configuration is restored
|
|
5
|
+
to the exact observed service baseline instead of being removed while DevPod
|
|
6
|
+
still references it.
|
|
7
|
+
|
|
8
|
+
1. Install `@devrouter/cli@0.0.40` on the host and bump `.devrouter.yml` to
|
|
9
|
+
`devrouter.version: 0.0.40`.
|
|
10
|
+
2. No schema, data, volume, or runtime migration is required.
|
|
11
|
+
3. Keep `.devcontainer/devcontainer.devrouter.json` ignored and owned by
|
|
12
|
+
devrouter. Do not delete it to recover a failed transition.
|
|
13
|
+
4. Retry the desired profile with `devrouter ensure`. If the repository-owned
|
|
14
|
+
post-start adapter still fails, correct that adapter before retrying.
|
|
15
|
+
|
|
16
|
+
Verification:
|
|
17
|
+
|
|
18
|
+
- Run `devrouter -V --repo <checkout>` and confirm both the installed CLI and
|
|
19
|
+
local repository report `0.0.40`.
|
|
20
|
+
- Run the repository's managed profile checks, including a cold transition
|
|
21
|
+
whose post-start adapter fails.
|
|
22
|
+
- Confirm the ignored generated configuration remains present after the
|
|
23
|
+
failure and `devrouter stop <checkout>` stops the exact DevPod without
|
|
24
|
+
deleting its workspace or volumes.
|
|
25
|
+
- Correct the post-start failure, rerun `devrouter ensure`, and confirm the
|
|
26
|
+
desired services, processes, and routes reconcile successfully.
|
|
27
|
+
|
|
28
|
+
Report template:
|
|
29
|
+
|
|
30
|
+
- CLI/config version: `0.0.40`
|
|
31
|
+
- Cold failure rollback: `<passed or details>`
|
|
32
|
+
- Exact non-destructive stop: `<passed or details>`
|
|
33
|
+
- Retry after correction: `<passed or details>`
|
|
34
|
+
- Remaining blockers: `<none or details>`
|
|
@@ -0,0 +1,43 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.0.41
|
|
2
|
+
|
|
3
|
+
Devrouter now supports Devsy as a first-class managed workspace runtime while
|
|
4
|
+
preserving the existing DevPod lifecycle and ownership guarantees.
|
|
5
|
+
|
|
6
|
+
1. Install `@devrouter/cli@0.0.41` on the host and bump `.devrouter.yml` to
|
|
7
|
+
`devrouter.version: 0.0.41`.
|
|
8
|
+
2. Run `devrouter setup --yes --workspace-runtime devsy` to make Devsy the
|
|
9
|
+
machine default for checkouts that neither registry owns yet. Existing
|
|
10
|
+
DevPod- and Devsy-owned checkouts continue to resolve by exact source path.
|
|
11
|
+
3. To enable Devsy inactivity shutdown for newly created workspaces, add
|
|
12
|
+
`--devsy-inactivity-timeout <duration>` to setup, for example
|
|
13
|
+
`devrouter setup --yes --workspace-runtime devsy --devsy-inactivity-timeout 30m`.
|
|
14
|
+
Omitting this option leaves existing per-workspace provider options intact.
|
|
15
|
+
4. Keep using `devrouter ensure`, `devrouter exec`, and `devrouter stop` for
|
|
16
|
+
managed lifecycle operations. Do not mutate the same workspace directly
|
|
17
|
+
with DevPod or Devsy commands because that bypasses devrouter's ownership
|
|
18
|
+
lock and route reconciliation.
|
|
19
|
+
5. No repository schema, data, volume, or devcontainer migration is required.
|
|
20
|
+
|
|
21
|
+
Verification:
|
|
22
|
+
|
|
23
|
+
- Run `devrouter -V --repo <checkout>` and confirm both the installed CLI and
|
|
24
|
+
local repository report `0.0.41`.
|
|
25
|
+
- Run `devrouter doctor --repo <checkout> --json` and confirm the effective
|
|
26
|
+
workspace runtime and its selection source are expected.
|
|
27
|
+
- Run `devrouter ensure <checkout> --json`, then
|
|
28
|
+
`devrouter exec <checkout> -- <representative-command>`.
|
|
29
|
+
- Confirm `devrouter workspace ls --json` joins the checkout to its exact
|
|
30
|
+
runtime registry owner (DevPod or Devsy), matching the runtime and source
|
|
31
|
+
reported by doctor, and that routed applications are reachable.
|
|
32
|
+
- Run `devrouter stop <checkout> --json`, then confirm the Devsy workspace is
|
|
33
|
+
stopped and `devrouter ls --json` contains no route for the exact checkout.
|
|
34
|
+
|
|
35
|
+
Report template:
|
|
36
|
+
|
|
37
|
+
- CLI/config version: `0.0.41`
|
|
38
|
+
- Effective runtime and source:
|
|
39
|
+
`<devsy/devpod and override/env/path-owner/machine-config/auto-detect/default>`
|
|
40
|
+
- Inactivity timeout: `<unset or duration>`
|
|
41
|
+
- Ensure/exec/route proof: `<passed or details>`
|
|
42
|
+
- Exact non-destructive stop: `<passed or details>`
|
|
43
|
+
- Remaining blockers: `<none or details>`
|