@volter/world 2.0.22 → 2.0.24
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.
|
@@ -72,7 +72,7 @@ ordinary `down`, or remove dependent branches first.
|
|
|
72
72
|
For existing operator configs, use the explicit name and root:
|
|
73
73
|
|
|
74
74
|
```bash
|
|
75
|
-
volter-world up <config> --root <twins-checkout> --env-
|
|
75
|
+
volter-world up <config> --root <twins-checkout> --env-out <new-output-env> --owner <task>
|
|
76
76
|
# From the app repo so the seed's SDK dependencies resolve:
|
|
77
77
|
volter-world attach <world> --root <twins-checkout> -- bun <seed-entry>
|
|
78
78
|
volter-world attach <world> --root <twins-checkout> -- <command...>
|
|
@@ -80,14 +80,14 @@ volter-world down <world> --root <twins-checkout>
|
|
|
80
80
|
```
|
|
81
81
|
|
|
82
82
|
The lower-level `volter-world up` starts a fresh instance: reseed after each successful boot.
|
|
83
|
-
Do not confuse this with the resumable `volter world up` API.
|
|
84
|
-
|
|
83
|
+
Do not confuse this with the resumable `volter world up` API. `up` WRITES the file passed to `--env-out`; it is never an input. Use a new disposable
|
|
84
|
+
output path, never credentials or custody. An init-generated preview is not the live output. Use `url` and `app-url` to discover endpoints rather
|
|
85
85
|
than parsing env files. Registered commands carry `VOLTER_WORLD`.
|
|
86
86
|
|
|
87
87
|
For a task that owns the entire lifecycle, use:
|
|
88
88
|
|
|
89
89
|
```bash
|
|
90
|
-
volter-world run <config> --root <twins-checkout> --env-
|
|
90
|
+
volter-world run <config> --root <twins-checkout> --env-out <new-output-env> --owner <task> -- <command...>
|
|
91
91
|
```
|
|
92
92
|
|
|
93
93
|
This operator command owns boot, its command and teardown. `--keep` makes it persistent.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@volter/world",
|
|
3
|
-
"version": "2.0.
|
|
3
|
+
"version": "2.0.24",
|
|
4
4
|
"description": "Run your app against a world of twins. `World` and `Repo` — one method per verb: init, up, run, log, diff, reset, branch, checkout, clone, fetch, changeset, push — and the `volter` command, one client of them.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"volter",
|
|
@@ -30,8 +30,8 @@
|
|
|
30
30
|
],
|
|
31
31
|
"dependencies": {
|
|
32
32
|
"@modelcontextprotocol/sdk": "^1.30.1",
|
|
33
|
-
"@volter/world-core": "2.0.
|
|
34
|
-
"@volter/world-runtime": "2.0.
|
|
33
|
+
"@volter/world-core": "2.0.14",
|
|
34
|
+
"@volter/world-runtime": "2.0.22",
|
|
35
35
|
"zod": "^4.6.5"
|
|
36
36
|
},
|
|
37
37
|
"peerDependencies": {
|
|
@@ -72,7 +72,7 @@ ordinary `down`, or remove dependent branches first.
|
|
|
72
72
|
For existing operator configs, use the explicit name and root:
|
|
73
73
|
|
|
74
74
|
```bash
|
|
75
|
-
volter-world up <config> --root <twins-checkout> --env-
|
|
75
|
+
volter-world up <config> --root <twins-checkout> --env-out <new-output-env> --owner <task>
|
|
76
76
|
# From the app repo so the seed's SDK dependencies resolve:
|
|
77
77
|
volter-world attach <world> --root <twins-checkout> -- bun <seed-entry>
|
|
78
78
|
volter-world attach <world> --root <twins-checkout> -- <command...>
|
|
@@ -80,14 +80,14 @@ volter-world down <world> --root <twins-checkout>
|
|
|
80
80
|
```
|
|
81
81
|
|
|
82
82
|
The lower-level `volter-world up` starts a fresh instance: reseed after each successful boot.
|
|
83
|
-
Do not confuse this with the resumable `volter world up` API.
|
|
84
|
-
|
|
83
|
+
Do not confuse this with the resumable `volter world up` API. `up` WRITES the file passed to `--env-out`; it is never an input. Use a new disposable
|
|
84
|
+
output path, never credentials or custody. An init-generated preview is not the live output. Use `url` and `app-url` to discover endpoints rather
|
|
85
85
|
than parsing env files. Registered commands carry `VOLTER_WORLD`.
|
|
86
86
|
|
|
87
87
|
For a task that owns the entire lifecycle, use:
|
|
88
88
|
|
|
89
89
|
```bash
|
|
90
|
-
volter-world run <config> --root <twins-checkout> --env-
|
|
90
|
+
volter-world run <config> --root <twins-checkout> --env-out <new-output-env> --owner <task> -- <command...>
|
|
91
91
|
```
|
|
92
92
|
|
|
93
93
|
This operator command owns boot, its command and teardown. `--keep` makes it persistent.
|