@voiden/runner 2.3.0-beta.5 → 2.3.0-beta.7
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/CHANGELOG.md +13 -0
- package/bundled-runners/voiden-faker-runner.js +13 -6
- package/bundled-runners/voiden-mcp-tool-runner.js +88 -88
- package/dist/index.js +1 -1
- package/dist/index.js.map +1 -1
- package/dist/mcpToolCapability.d.ts +5 -0
- package/dist/mcpToolCapability.d.ts.map +1 -1
- package/dist/mcpToolCapability.js.map +1 -1
- package/dist/runtimeVars.d.ts.map +1 -1
- package/dist/runtimeVars.js +18 -0
- package/dist/runtimeVars.js.map +1 -1
- package/package.json +7 -2
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,19 @@
|
|
|
3
3
|
All notable changes to `@voiden/runner` are documented here. This package is
|
|
4
4
|
versioned and released independently of the Voiden desktop app.
|
|
5
5
|
|
|
6
|
+
## v2.3.0-beta.7 - 2026-08-11
|
|
7
|
+
|
|
8
|
+
### Fixed
|
|
9
|
+
- `mcp install`/`mcp uninstall` no longer corrupt `~/.codex/config.toml` — the section-matching regex stopped at the first `[` it saw, which was the `args = [...]` array inside the `[mcp_servers.voiden-mcp]` table itself, so it never consumed that line. A re-install left the old `args` array orphaned as a dangling, unparseable line; an uninstall left it behind entirely, breaking the file for Codex on next launch. Bumps `@voiden/executors` to `0.1.6` for the underlying fix.
|
|
10
|
+
|
|
11
|
+
## v2.3.0-beta.6 - 2026-08-07
|
|
12
|
+
|
|
13
|
+
### Added
|
|
14
|
+
- `source: environment` toolparams can now pin their own `envProfile`/`envName`, resolving that exact profile/environment regardless of how many the project has — previously this only ever auto-resolved when the project had exactly one environment, and silently resolved nothing otherwise. Params without either field keep the old single-environment auto-detect behavior, so existing tools need no changes.
|
|
15
|
+
|
|
16
|
+
### Fixed
|
|
17
|
+
- A tool's verification requests now see the same environment-resolved values a real agent call would — `source: environment` params were previously only resolved for actual tool calls, never for verification, so any tool using one would always fail verification (and get withdrawn) even though the tool itself worked fine when called directly.
|
|
18
|
+
|
|
6
19
|
## v2.3.0-beta.5 - 2026-08-06
|
|
7
20
|
|
|
8
21
|
### Fixed
|