@devrouter/cli 0.0.64 → 0.0.65
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 +5689 -2382
- package/dist/devrouter.js +2626 -670
- package/package.json +1 -1
- package/upgrade-prompts/0.0.65.md +39 -0
package/package.json
CHANGED
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.0.65
|
|
2
|
+
|
|
3
|
+
This feature release adds managed-workspace network capacity support: read-only
|
|
4
|
+
capacity and retained-ownership diagnostics plus opt-in daemon-bound subnet
|
|
5
|
+
allocation for new managed linked-workspace Compose networks.
|
|
6
|
+
|
|
7
|
+
## Task
|
|
8
|
+
|
|
9
|
+
Install the published release and update `.devrouter.yml` devrouter.version to
|
|
10
|
+
0.0.65. No schema migration is required. Opting a repository in needs two
|
|
11
|
+
operator steps: install `~/.config/devrouter/network-policy.json` naming
|
|
12
|
+
private pools, exclusions and permitted prefixes for the exact Docker daemon,
|
|
13
|
+
then add `managedRuntime.network` to the repository configuration. Repository
|
|
14
|
+
configuration cannot select address ranges. Adding a policy changes nothing for
|
|
15
|
+
existing workspaces, networks or provider registrations.
|
|
16
|
+
|
|
17
|
+
## Validation
|
|
18
|
+
|
|
19
|
+
Run `devrouter doctor --repo <checkout> --json` and confirm the read-only
|
|
20
|
+
network capacity report. On an authorized runtime with a valid policy, start a
|
|
21
|
+
new managed linked workspace and verify the ignored generated Compose overlay,
|
|
22
|
+
the persisted subnet claim, exact provider destination reuse, and subnet
|
|
23
|
+
retention across stop and resume. Verify failure paths retain claims and never
|
|
24
|
+
delete networks, containers or workspaces. Stop the exact runtime afterwards
|
|
25
|
+
and confirm zero routes with retained data.
|
|
26
|
+
|
|
27
|
+
## Limits
|
|
28
|
+
|
|
29
|
+
Allocation requires complete route and daemon evidence; virtualized contexts
|
|
30
|
+
such as OrbStack stay diagnostics-only until guest routes are qualified.
|
|
31
|
+
Existing `/24` networks are never subdivided or migrated. Stopping a workspace
|
|
32
|
+
or removing its worktree does not release a subnet, and cleanup remains
|
|
33
|
+
report-only. Without a policy, allocation behavior is unchanged.
|
|
34
|
+
|
|
35
|
+
## Report
|
|
36
|
+
|
|
37
|
+
Report installed version, policy presence without its contents, diagnostic
|
|
38
|
+
output, allocation outcomes with synthetic receipts, and any retained claims or
|
|
39
|
+
resources. Separate published source, synthetic checks and live runtime proof.
|