@devrouter/cli 0.3.0 → 0.4.0
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 +2 -2
- package/dist/devrouter.js +477 -147
- package/package.json +1 -1
- package/upgrade-prompts/0.3.1.md +27 -0
- package/upgrade-prompts/0.4.0.md +39 -0
package/package.json
CHANGED
|
@@ -0,0 +1,27 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.3.1
|
|
2
|
+
|
|
3
|
+
This patch release makes the `workspace leftover` output readable. Each stack's
|
|
4
|
+
table row now shows per-kind counts, for example `removed 7 container(s), 42
|
|
5
|
+
volume(s), 1 network(s)`, instead of every removed container ID and volume
|
|
6
|
+
name. After an apply, one line points to the per-stack receipts and `--json`,
|
|
7
|
+
which still list every object.
|
|
8
|
+
|
|
9
|
+
There is no configuration change, no migration and no change to which objects
|
|
10
|
+
are removed.
|
|
11
|
+
|
|
12
|
+
## Task
|
|
13
|
+
|
|
14
|
+
Install the published 0.3.1 CLI. No repository change is needed. A repository
|
|
15
|
+
that requires 0.3.0 keeps working with 0.3.1.
|
|
16
|
+
|
|
17
|
+
## Validation
|
|
18
|
+
|
|
19
|
+
1. Run `devrouter -V` from the consumer checkout. A repository Volta pin can
|
|
20
|
+
change which install resolves.
|
|
21
|
+
2. Optionally run `devrouter workspace leftover --manifest <file> --sha256
|
|
22
|
+
<hash>` as a dry run and confirm each stack shows one row of counts.
|
|
23
|
+
|
|
24
|
+
## Report
|
|
25
|
+
|
|
26
|
+
Report the release revision and the resolved executable with its installed
|
|
27
|
+
version.
|
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.4.0
|
|
2
|
+
|
|
3
|
+
This minor release adds `devrouter env`, which gives host-run tools such as
|
|
4
|
+
Playwright, `psql` or Prisma the endpoints of a checkout's managed runtime.
|
|
5
|
+
|
|
6
|
+
- `devrouter env [path] [--json]` reports the checkout's routed HTTPS URLs,
|
|
7
|
+
the routed TLS/SNI and published loopback endpoints of its TCP apps, the
|
|
8
|
+
workspace token and the mkcert CA path. The JSON report has `version: 1`.
|
|
9
|
+
- `devrouter env [path] -- <command...>` runs a host command without a shell.
|
|
10
|
+
It exports `DEVROUTER_WORKSPACE`, `DEVROUTER_<APP>_URL`,
|
|
11
|
+
`DEVROUTER_<APP>_HOST`/`_PORT` (loopback) and
|
|
12
|
+
`DEVROUTER_<APP>_ROUTED_HOST`/`_ROUTED_PORT`, plus `NODE_EXTRA_CA_CERTS`
|
|
13
|
+
when it is unset, and returns the command's exit code.
|
|
14
|
+
|
|
15
|
+
The command only reads state. It never starts or stops a runtime and prints no
|
|
16
|
+
credentials. A loopback endpoint is reported only when exactly one running
|
|
17
|
+
container of this checkout's devcontainer owns the upstream alias and
|
|
18
|
+
publishes the port on a loopback address; otherwise the report names the
|
|
19
|
+
reason. There is no configuration change and no migration.
|
|
20
|
+
|
|
21
|
+
## Task
|
|
22
|
+
|
|
23
|
+
Install the published 0.4.0 CLI. No repository change is needed. A repository
|
|
24
|
+
that requires 0.3.x keeps working with 0.4.0. Raise a repository's documented
|
|
25
|
+
minimum devrouter version to 0.4.0 only when consumer source changes are
|
|
26
|
+
authorized and a host script should use `devrouter env` instead of its own
|
|
27
|
+
port discovery.
|
|
28
|
+
|
|
29
|
+
## Validation
|
|
30
|
+
|
|
31
|
+
1. Run `devrouter -V` from the consumer checkout. A repository Volta pin can
|
|
32
|
+
change which install resolves.
|
|
33
|
+
2. With the runtime running, run `devrouter env . --json` and confirm the app
|
|
34
|
+
URLs and loopback ports match `devrouter status` and `docker port`.
|
|
35
|
+
|
|
36
|
+
## Report
|
|
37
|
+
|
|
38
|
+
Report the release revision, the resolved executable with its installed
|
|
39
|
+
version, and any loopback reason other than a running endpoint.
|