@voiden/runner 2.3.0-beta.2 → 2.3.0-beta.4
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 +26 -0
- package/bundled-runners/voiden-mcp-tool-runner.js +87 -87
- package/dist/index.js +2 -2
- package/dist/index.js.map +1 -1
- package/dist/mcpServing.js +1 -1
- package/dist/mcpServing.js.map +1 -1
- package/dist/mcpToolCapability.d.ts +2 -2
- package/dist/mcpToolCapability.d.ts.map +1 -1
- package/dist/mcpToolCapability.js +3 -3
- package/dist/mcpToolCapability.js.map +1 -1
- package/dist/runner.d.ts.map +1 -1
- package/dist/runner.js +7 -2
- package/dist/runner.js.map +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,32 @@
|
|
|
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.4 - 2026-08-06
|
|
7
|
+
|
|
8
|
+
### Fixed
|
|
9
|
+
- A served `/tool`'s `source: environment` param now actually resolves from
|
|
10
|
+
the project's `.voiden/env-public.yaml` / `.voiden/env-private.yaml` files
|
|
11
|
+
(private overrides public), not just the bare `@voiden/mcp-server` process's
|
|
12
|
+
own OS environment. Deliberately simplified vs. the app's full environment
|
|
13
|
+
system — no profiles, no hierarchical/child environments, no "active
|
|
14
|
+
environment" selection (nothing to select from headlessly) — only resolves
|
|
15
|
+
when a project has exactly one environment defined; ambiguous otherwise.
|
|
16
|
+
|
|
17
|
+
## v2.3.0-beta.3 - 2026-08-06
|
|
18
|
+
|
|
19
|
+
### Fixed
|
|
20
|
+
- A verify entry (or a tool's own home section) targeting a file with no
|
|
21
|
+
`request-separator` blocks — i.e. a file that's just one request, with no
|
|
22
|
+
real "sections" to disambiguate between — no longer requires its
|
|
23
|
+
`sectionLabel` to exactly match anything. Previously an unlabeled first
|
|
24
|
+
section's real label (`undefined`, from `parseVoidFileSections()`) never
|
|
25
|
+
matched a saved label like `"Request 1"`, so any tool verifying against
|
|
26
|
+
such a file was incorrectly excluded as `missing-section` even though the
|
|
27
|
+
target was unambiguous. `runVoidFile()`, and both the headless and
|
|
28
|
+
Electron-app tool-capability implementations, now treat a single-section
|
|
29
|
+
file as always resolving to its one request regardless of what
|
|
30
|
+
`sectionLabel` (or none) was given.
|
|
31
|
+
|
|
6
32
|
## v2.3.0-beta.2 - 2026-08-06
|
|
7
33
|
|
|
8
34
|
Published out of lockstep with the desktop app (still `2.3.0-beta.1`) — this
|