Skip to content

0.5.1 — the 0.5.0 tarball could not be installed

Choose a tag to compare

@lenucksi lenucksi released this 05 Oct 07:35
· 143 commits to local/modernized since this release

The 0.5.0 tarball could not be installed. This release fixes that and changes nothing else.

What was wrong

package.json declared patchedDependencies pointing at patches/ghostty-web.patch, but files listed only dist. The published package therefore contained a manifest referring to a patch it did not ship, and bun install in the extracted package failed with Couldn't find patch file.

It only shows up when you install the artifact — from a checkout the patch is sitting right there.

A note on the lockfile

Shipping bun.lock was considered and is not the fix. Neither npm pack nor bun pm pack includes it, which is why installing the tarball resolves ranges and lands on @opencode/plugin 2.0.23 rather than the locked 2.0.22. That is ordinary npm behaviour: clone the repository and you get exactly the tested graph, install the tarball and you get the newest matching versions.

Verified from this tarball, not from a checkout

  • bun install --production succeeds, 285 packages
  • pty_spawn returns <pty_spawned id=... cols=... rows=...>
  • the id appears in pty_list
  • pty_screen returns the rendered text
  • a file that exists but is not executable is refused before the spawn

See CHANGELOG.md for the 0.5.0 changes.