Commit Graph
1 Commits
Author SHA1 Message Date
dependabot[bot]andJerrettDavis 99e223c0e2 deps: Bump tsup from 8.5.1 to 9.0.0 in /plugins/opencode (#4385)
Build the OpenCode plugin with the patched esbuild line inside tsup's
supported range. Headroom's existing esbuild 0.28 security override is
outside tsup 8.5.1's ^0.27.0 declaration. Tsup 9 declares ^0.28.2, so
retain the major upgrade and raise the override floor from ^0.28.1 to
^0.28.2. The original tsup 9 lock still selected 0.28.1; this follow-up
corrects that mismatch and documents the source-build requirements.

## Dependency assessment

- **Version reason:** use an upstream-supported build combination for
the existing dependency-security mitigation, rather than forcing the
selected esbuild release outside the old bundler's range. This does not
claim a new advisory in 0.28.1 or that the old built plugin was
demonstrated broken. Tsup remains the existing builder;
[v9](https://github.com/egoist/tsup/releases/tag/v9.0.0) also changes
debug/obug, watchers and related toolchain packages.
- **Maintenance/security:** reviewed the published release/manifest and
resolved graph. Fresh audit reports zero vulnerabilities; this does not
imply every upstream project has a spotless history. Platform-selector
metadata outside the esbuild refresh is preserved instead of accepting
unrelated npm-version normalization.
- **Node/build boundary:** tsup requires `^22.18.0 || ^24.11.0 ||
>=26.0.0`; the current graph's ini 7 also requires `^22.22.2 || ^24.15.0
|| >=26.0.0`. The README documents both and the verified Node 24.22.2
choice. Published plugin/host runtime declarations are unchanged. An
earlier Node 22.22.0 pass emitted the existing ini warning; acceptance
uses the supported Node 24 install.
- **Native/install/network:** existing esbuild/Rollup platform code and
lifecycle scripts remain build inputs. Rollup's optional GNU Linux-x64
LZMA and Android-x64 bindings are present; the LZMA entry is a real
optional dependency, not an orphan. Windows x64 installation/build was
tested; these non-Windows paths were not. No new install-script flag is
introduced. Existing plugin runtime dependencies are unchanged; tsup
remains a development dependency. npm and host support-dependency
installation use the registry. No plugin is published and no
inference/provider message is requested.

The branch is synchronized with main's merged security and SDK updates.

## Real behavior proof

Windows x64 / Node 24.22.2 / npm 10.9.4, fresh isolated checkout. From
`plugins/opencode`, under that Node:

```bash
npm ci --ignore-scripts=false --no-audit --no-fund
npm test
npm run typecheck
npm run build
npm run build:standalone
npm audit --json
node ../../scripts/verify_opencode_bundle.mjs .
```

The install has no engine warning; **61 tests pass**, typecheck and both
builds succeed, audit reports zero vulnerabilities. The committed
portable proof imports actual `dist/index.js` and
`dist-standalone/index.js`, invokes the built server entry and performs
real chat/retrieve HTTP requests against an ephemeral loopback fixture.
It asserts original upstream/path, project/session headers, response and
retrieval content; output reports PASS. The plugin routes the synthetic
OpenAI URL to the fixture. Hooks/sockets/processes are disposed. This is
built-artifact wire behavior, not a claim that the fixture is the Python
service.

**Actual host loading:** installed official `opencode-ai@1.19.4`,
matching the installed 1.x plugin SDK, into a task-only prefix/cache.
Its native Windows `opencode.cmd debug config --print-logs` ran from an
isolated task workspace with the built main entry
`file:///G:/git/headroom-dep4385/plugins/opencode/dist/index.js`
configured directly. No wrapper was used for this check. It exited 0
with successful bootstrap/configuration/disposal and no loader error. A
separate instrumentation probe preserved the exported object shape and
delegated its actual `server` function; it recorded `id=headroom`,
retrieval-tool registration and the shell-environment hook. It did not
adapt the object into a legacy function.

The host's XDG config/data/state/cache point at task-only directories.
Enabled providers are empty; auto-update, remote model fetching and
default plugins are disabled. Credential environment names are removed
in the child shell only; user home/config/auth files are not repurposed.
The CLI installed support dependencies in the isolated config, so
registry traffic occurred. No inference command or provider action was
requested.

Node syntax and whitespace checks pass. Independent technical review
found no code or dependency-policy blocker in the corrected build
range/source-runtime boundaries.

Untested: actual OpenCode 2.x, registry-tarball plugin installation, the
Python compression proxy in this smoke, streaming, live providers,
hook-shim spawning, non-Windows native installation, or production
publishing. Current-head hosted CI must pass before approval.

---------

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>
2026-11-03 08:45:19 -06:00