@devrouter/cli 0.0.44 → 0.0.46
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 +668 -249
- package/package.json +1 -1
- package/upgrade-prompts/0.0.45.md +33 -0
- package/upgrade-prompts/0.0.46.md +41 -0
package/package.json
CHANGED
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.0.45
|
|
2
|
+
|
|
3
|
+
Parallel linked worktrees now claim collision-safe workspace identities across
|
|
4
|
+
mixed DevPod and Devsy fleets.
|
|
5
|
+
|
|
6
|
+
1. Install `@devrouter/cli@0.0.45` on the host and bump `.devrouter.yml` to
|
|
7
|
+
`devrouter.version: 0.0.45`.
|
|
8
|
+
2. Keep using `devrouter ensure <checkout>` or `devrouter workspace up
|
|
9
|
+
<branch>`. Do not derive workspace ids or worktree paths in wrapper scripts.
|
|
10
|
+
3. Existing persisted workspace identities stay unchanged. A genuinely new
|
|
11
|
+
checkout keeps its readable branch/path identity when free and receives a
|
|
12
|
+
deterministic hash-suffixed fallback only when another checkout or provider
|
|
13
|
+
already occupies that identity.
|
|
14
|
+
4. Treat an unreadable DevPod or Devsy registry as a startup blocker for a new
|
|
15
|
+
claim. Devrouter fails before provider, process, service, or route mutation.
|
|
16
|
+
|
|
17
|
+
Verification:
|
|
18
|
+
|
|
19
|
+
- Run `devrouter -V --repo <checkout>` and confirm the installed CLI and local
|
|
20
|
+
repository report `0.0.45`.
|
|
21
|
+
- Start two new linked checkouts whose branch names share the first 32
|
|
22
|
+
sanitized characters, one with DevPod and one with Devsy.
|
|
23
|
+
- Require distinct persisted workspace ids, exact provider registrations, and
|
|
24
|
+
namespaced routes. Stop each checkout with `devrouter stop <checkout>` and
|
|
25
|
+
require both route sets to disappear.
|
|
26
|
+
|
|
27
|
+
Report template:
|
|
28
|
+
|
|
29
|
+
- CLI/config version: `0.0.45`
|
|
30
|
+
- Colliding-prefix identities: `<passed or details>`
|
|
31
|
+
- DevPod/Devsy ownership: `<passed or details>`
|
|
32
|
+
- Exact stop and route release: `<passed or details>`
|
|
33
|
+
- Remaining blockers: `<none or details>`
|
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.0.46
|
|
2
|
+
|
|
3
|
+
Provider mutations under parallel agent load are now observable and drain a
|
|
4
|
+
realistic queue of cold starts instead of failing after a silent minute.
|
|
5
|
+
|
|
6
|
+
1. Install `@devrouter/cli@0.0.46` on the host and bump `.devrouter.yml` to
|
|
7
|
+
`devrouter.version: 0.0.46`.
|
|
8
|
+
2. No schema or command changes. Keep using `devrouter ensure <checkout>` and
|
|
9
|
+
`devrouter workspace up <branch>`.
|
|
10
|
+
3. When several parallel `ensure` runs contend for the machine-global
|
|
11
|
+
Devsy/DevPod mutation lock, contenders now wait up to thirty minutes in
|
|
12
|
+
fair arrival order and print one throttled stderr line every ten seconds.
|
|
13
|
+
Do not treat those lines as failures; a timeout names the queue position or
|
|
14
|
+
holder PID plus true durations and usually means the holder process died
|
|
15
|
+
mid-start or a direct provider command bypassed devrouter.
|
|
16
|
+
4. If a Devsy start fails with the agent-binary acquisition remediation,
|
|
17
|
+
allow Devsy to download its agent binary or export `DEVSY_AGENT_BINARY`
|
|
18
|
+
pointing at a verified official Devsy agent binary matching this platform
|
|
19
|
+
and Devsy version. Do not point it at an arbitrary binary.
|
|
20
|
+
5. A checkout whose persisted managed state names a Compose project that no
|
|
21
|
+
longer has any exact containers can now rebaseline on its currently
|
|
22
|
+
observed exact workspace. If prior-project containers still exist, repair
|
|
23
|
+
that drift explicitly; Devrouter continues to fail closed.
|
|
24
|
+
|
|
25
|
+
Verification:
|
|
26
|
+
|
|
27
|
+
- Run `devrouter -V --repo <checkout>` and confirm the installed CLI and
|
|
28
|
+
local repository report `0.0.46`.
|
|
29
|
+
- Start two linked checkouts concurrently with `devrouter ensure` and require
|
|
30
|
+
both to succeed with visible wait progress on the second, or a timeout
|
|
31
|
+
error that names the holder PID and durations.
|
|
32
|
+
- When changing a checkout's workspace runtime, run one capability-only and
|
|
33
|
+
one routed profile and inspect `managedRuntime.drift`; require an empty list.
|
|
34
|
+
|
|
35
|
+
Report template:
|
|
36
|
+
|
|
37
|
+
- CLI/config version: `0.0.46`
|
|
38
|
+
- Parallel ensure contention: `<passed or details>`
|
|
39
|
+
- Wait progress output: `<observed or details>`
|
|
40
|
+
- Managed-state rebaseline/profile transition: `<passed or details>`
|
|
41
|
+
- Remaining blockers: `<none or details>`
|