@voiden/runner 2.3.0-beta.12 → 2.3.0-beta.14

package/CHANGELOG.md

@@ -3,6 +3,18 @@
 All notable changes to `@voiden/runner` are documented here. This package is
 versioned and released independently of the Voiden desktop app.
 
+## v2.3.0-beta.14 - 2026-08-26
+
+### Fixed
+- `plugin list`'s core-plugin status badge now checks whether a `runner.js` actually exists (bundled in this package install, or cached in `~/.voiden/extensions/<id>/runner.js`), not just whether the plugin is enabled in `~/.voiden/plugins.json`. Previously it could report "✓ enabled" for a plugin with no usable runner anywhere — exactly the state `loadEnabledPlugins()` treats as unavailable at request-run time (`activePlugins: []`, "not installed" errors from `run_request`) — so the two disagreed with no way to tell why. Now shows "not installed [no runner]" in that case, matching what actually gets loaded.
+- A `linkedBlock`/`linkedFile` pointer node could get resolved as if it *were* the target content instead of the real block it points to, when its own `uid` collided with the `blockUid` being searched for (e.g. a hand-authored file that copied a block's `uid` onto the wrapper instead of generating a fresh one, most likely when linking a block into the same file it lives in). `resolveLinkedBlocks`/`resolveLinkedFiles` now exclude `linkedBlock`/`linkedFile` nodes from ever matching as resolved content — a colliding `uid` now resolves to the real block if one still carries it, or is left unresolved, instead of silently substituting the pointer itself. `@voiden/executors` bumped to `0.1.9`.
+
+## v2.3.0-beta.13 - 2026-08-21
+
+### Fixed
+- `linkedBlock`/`linkedFile` imports (a shared headers/auth/body block reused across requests, or a whole section imported from another file) now resolve when running headlessly — previously only the Voiden app resolved these (built on `window.electron`, React Query, and a live editor), so a request that only got its headers/auth/body from an imported block silently sent without them when run via `voiden-runner` or `voiden-mcp` — no error, just an empty header set. `@voiden/executors` bumped to `0.1.8`, which adds the resolver (`resolveLinkedBlocks`/`resolveLinkedFiles`); `originalFile` paths resolve against a new `projectRoot` (matching the Tool block's own `requestFilePath` convention — the `run` command defaults it to `process.cwd()`, `mcp`/`tool` commands pass their existing project directory through).
+- Multipart file uploads (`multipart-table`, including `fileLink`/file attachments) and raw binary request bodies (`restFile`) are now supported when running headlessly — previously unsupported outright rather than just import-broken, even though the network layer (`@voiden/executors`' `secureRequest.ts`) already fully handled multipart `FormData` and binary uploads. Fixed upstream in `plugin-voiden-rest-api`'s `runner.ts` (now reuses the app's own `requestBuilder.ts` body-building logic instead of the headless parser only ever handling json/xml/yml bodies), re-bundled here.
+
 ## v2.3.0-beta.8 - 2026-08-11
 
 ### Fixed

package/bundled-runners/versions.json

@@ -1,11 +1,11 @@
 {
-  "simple-assertions": "1.0.4",
-  "voiden-advanced-auth": "2.0.7",
-  "voiden-faker": "1.1.0",
-  "voiden-graphql": "1.0.6",
-  "voiden-mcp-client": "0.1.0",
-  "voiden-mcp-tool": "0.1.0",
-  "voiden-rest-api": "1.4.8",
+  "simple-assertions": "1.0.5",
+  "voiden-advanced-auth": "2.0.8",
+  "voiden-faker": "1.1.1",
+  "voiden-graphql": "1.0.7",
+  "voiden-mcp-client": "0.1.1",
+  "voiden-mcp-tool": "0.1.1",
+  "voiden-rest-api": "1.4.12",
   "voiden-scripting": "1.1.6",
-  "voiden-sockets-grpcs": "1.1.6"
+  "voiden-sockets-grpcs": "1.1.7"
 }