opencode (1.18.21-0parrot2) unstable; urgency=medium

  * No Node.js relationship: opencode runs entirely on its embedded Bun
    runtime and does not need Node.js. (Optional Node-based LSP servers and
    the npm plugin/upgrade path use a system node if the user happens to have
    one, but the package neither needs nor references one.)

 -- Parrot Security <team@parrotsec.org>  Tue, 24 Aug 2026 00:45:00 +0200

opencode (1.18.21-0parrot1) unstable; urgency=medium

  * Initial Debian packaging of opencode (opencode.ai) v1.18.21.
  * Build from the upstream source tarball with the Bun toolchain.
    opencode is a Bun-native application: the CLI is produced by
    `bun build --compile` as a self-contained binary (Bun runtime and all
    JS dependencies embedded), so the package has no Node.js runtime
    dependency.
  * Bun is not packaged in Debian, so the Bun toolchain is downloaded from
    the network at build time (pinned to the version required by upstream's
    packageManager field, bun@1.3.14).
  * npm dependencies are installed at build time with `bun install`, pinned
    by the upstream bun.lock; the models.dev provider catalog used for code
    generation is fetched from the network as well. The build therefore
    requires a network-enabled build worker and will not run offline.
  * The build targets the build host's architecture only (--single) and runs
    upstream's smoke test (opencode --version). The optional embedded web UI
    is not included; the TUI, headless server and CLI are fully functional.
  * Redirect HOME to a writable dir inside the build tree
    (debian/fakehome) so bun's install cache/tmp work under sbuild, which
    sets HOME=/sbuild-nonexistent (fixes EACCES "mkdir /sbuild-nonexistent").

 -- Parrot Security <team@parrotsec.org>  Sun, 23 Aug 2026 22:40:00 +0200
