deps: Bump tsup from 8.5.1 to 9.0.0 in /plugins/openclaw (#4384)

Use tsup 9's supported esbuild 0.28 build combination for the OpenClaw
plugin. Headroom's existing security override selected ^0.28.1 outside
tsup 8.5.1's ^0.27.0 range. Tsup 9 declares ^0.28.2; retain the upgrade
and raise the override floor to ^0.28.2 so the locked compiler satisfies
it. Preserve unrelated native-platform metadata and document the
source-build Node requirement.

## Dependency assessment

- **Why version:** keep the existing builder while making the patched
esbuild choice an upstream-supported combination. This is compatibility
work for the existing security build inputs, not cosmetic currency, a
new 0.28.1 advisory claim, or evidence that the old plugin failed.
[Official v9
changes](https://github.com/egoist/tsup/releases/tag/v9.0.0) cover
esbuild/chokidar and debug/obug transitions.
- **Maintenance/security:** upstream release/manifest and resolved
packages were reviewed. Fresh plugin audit reports zero vulnerabilities;
this is not a guarantee about all upstream security history. Plugin
runtime logic is unchanged.
- **Build/host boundary:** source builds require `^22.18.0 || ^24.11.0
|| >=26.0.0` for tsup 9. The README separates that range from the
OpenClaw host runtime. Node 24.22.2 was used for acceptance and actual
OpenClaw 2026.10.6 loading; other host/runtime combinations are not
claimed tested.
- **Native/install/network:** esbuild's native binary selection/install
lifecycle and Rollup's optional platform packages remain development
inputs, including the new GNU Linux-x64 LZMA package. It is a real
Rollup optional dependency. Windows x64 installation/build is qualified;
Linux/macOS/other bindings are not. No new install-script flag is
introduced. The packed plugin uses built dist code and its existing
headroom-ai runtime dependency; bundler tooling remains
development-only. Registry downloads/lifecycle code run during
installation. Host inspection is credential-free and starts no
gateway/provider action.

The original UTF-8 package description is preserved; the final manifest
difference from the bot head is the esbuild override floor. Main's
security/SDK updates are included.

## Real behavior proof

Windows x64 / Node 24.22.2, isolated checkout. From `plugins/openclaw`,
using npm under that Node:

```bash
npm ci --ignore-scripts=false --no-audit --no-fund
npm test
npm run typecheck
npm run build
npm audit --json
```

Fresh installation succeeds, **129 tests across 8 files pass**,
typecheck and ESM/declaration build pass, audit reports zero
vulnerabilities. Importing the built module and invoking registration
constructs its context engine and registers retrieval/gateway-start
hooks with no proxy autostart or provider configured.

**Actual host loading:** official `openclaw@2026.10.6` (`fe06181`) on
Node 24.22.2 ran `openclaw plugins list --json` with task-isolated
OPENCLAW_STATE_DIR and OPENCLAW_CONFIG_PATH. The config is:

```json
{"plugins":{"allow":["headroom"],"load":{"paths":["G:/git/headroom-dep4384/plugins/openclaw"]},"slots":{"contextEngine":"headroom"},"entries":{"headroom":{"enabled":true,"config":{"autoStart":false,"gatewayProviderIds":[],"routeCodexViaProxy":false}}}}}
```

The CLI exited 0 and reported headroom with status loaded, source
`plugins/openclaw/dist/index.js`, and tool `headroom_retrieve`; no
plugin load error was reported. Its runtime dependency was installed.
The isolated first run used a derived registry (an informational
missing-persisted-registry note), not user plugin state. No gateway was
started, proxy spawned, provider invoked or message sent. This validates
actual host loading, not merely a mock registration API.

Whitespace checks pass. The UTF-8 metadata preservation does not change
the built module; after the later clean main merge, plugin files are
otherwise identical to the qualified component.

Untested: inference, real compression proxy requests, gateway/provider
routing, other host versions/platforms, non-Windows native installation,
registry-tarball plugin installation, or production publishing.
Current-head hosted CI remains required.

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: JerrettDavis <mxjerrett@gmail.com>
This commit is contained in:
dependabot[bot]
2026-11-04 22:49:39 -06:00
committed by GitHub
co-authored by JerrettDavis
parent a8375a1d26
commit 9d87151610
3 changed files with 330 additions and 295 deletions
+3
View File
@@ -23,6 +23,9 @@ This plugin can auto-start a local `headroom proxy` when needed. OpenClaw treats
## Local Development Install (Detection-Friendly)
Building from source requires Node.js `^22.18.0 || ^24.11.0 || >=26.0.0` for the tsup 9 toolchain. Use a supported Node release before running `npm ci` and `npm run build`. This is a source-build requirement; the published plugin uses the Node runtime supported by your OpenClaw host and does not run tsup during plugin loading.
If you are testing from this repo, run npm install/build from the plugin directory so local launcher detection aligns with runtime paths. These linked installs are supported:
```bash
+325 -293
View File
File diff suppressed because it is too large Load Diff
+2 -2
View File
@@ -31,12 +31,12 @@
"devDependencies": {
"@typescript/native": "npm:typescript@^7.0.2",
"@types/node": "^26.1.1",
"tsup": "^8.0.0",
"tsup": "^9.0.0",
"typescript": "^6.0.3",
"vitest": "^5.0.0"
},
"overrides": {
"esbuild": "^0.28.1"
"esbuild": "^0.28.2"
},
"openclaw": {
"hooks": [