#159 chore(deps): bump bun-pty from 0.4.10 to 0.5.1

Sourced from bun-pty's releases.

v0.5.1

Fixed

• Test files are left out of the npm package (#50)
  • "files" in package.json lists all of src, and npm does not apply .npmignore patterns to the paths it lists, so earlier tarballs included the src/*.test.ts files
  • No code changes since 0.5.0. See the 0.5.0 notes for the env change

v0.5.0

⚠️ Breaking: env replaces the child's environment

env is now the child's whole environment, as in node-pty, instead of being merged over the parent's. Variables you leave out, such as tokens, no longer reach the child (#47).

If you pass a partial map and rely on inheriting the rest, spread process.env:

spawn("bash", [], { name: "xterm-256color", env: { ...process.env, FOO: "bar" } });

If you already pass { ...process.env, ... } or no env, nothing changes for you.

Changed

• env replaces the environment (#48)
  • Without env, the child gets the current process.env, so changes made at runtime reach it
  • When the map has no PATH, a bare program name such as sh is still found with the parent's PATH, which does not reach the child
  • On Windows, a map with no entries keeps the parent's environment, as in node-pty
• The child's environment is built as node-pty builds it on Unix (#49)
  • TERM is set from the name option, which was ignored before, then from TERM in the environment, then "xterm"
  • PWD is set from cwd
  • When the child inherits process.env, the parent's tmux and screen variables (TMUX, STY, ...) and its COLUMNS and LINES are dropped
• IPtyForkOptions.name is optional, and env: process.env now type-checks (#49)

Thanks to @​zgeoff for the report and the contribution!

v0.4.11

Added

• Native Windows ARM64 support (#46)
  • Ships a pre-built rust_pty_arm64.dll (built on GitHub's windows-11-arm runner for aarch64-pc-windows-msvc) alongside the existing x64 rust_pty.dll, whose filename is unchanged
  • Links the MSVC runtime statically (-C target-feature=+crt-static) to avoid a Visual C++ Redistributable dependency
  • Selects the ARM64 DLL at runtime and in the bun build --compile embed path, falling back to rust_pty.dll
  • Adds a windows-11-arm job to the test matrix that runs the unit and integration tests against the exact ARM64 artifact

Thanks to @​dakehero for the contribution!

Sourced from bun-pty's changelog.

[0.5.1] - 2026-10-12

Fixed

• Leave the src/*.test.ts files out of the npm package (#50)
  • "files" in package.json lists all of src, and npm does not apply .npmignore patterns to the paths it lists, so earlier tarballs included the tests

[0.5.0] - 2026-10-12

Changed

• Breaking: env is now the child's whole environment, as in node-pty, instead of being merged over the parent's (#48)
  • To keep inherited variables, spread process.env: env: { ...process.env, FOO: "bar" }
  • Without env, the child gets the current process.env, so changes made at runtime reach it (before, it got the environment the process started with)
  • When the map has no PATH, a bare program name such as sh is still found with the parent's PATH, which does not reach the child; on Unix, argv[0] is then the resolved path
  • On Windows, a map with no entries keeps the parent's environment, as in node-pty
• On Unix, the child's environment is now built as node-pty builds it (#49)
  • TERM is set from the name option, then from TERM in the environment, then "xterm"; name was ignored before
  • PWD is set from cwd
  • When the child inherits process.env, the parent's tmux and screen variables (TMUX, TMUX_PANE, STY, WINDOW, WINDOWID, TERMCAP) and its COLUMNS and LINES are dropped
• IPtyForkOptions.name is optional, and env accepts undefined values, which are skipped, so env: process.env type-checks (#49)

Fixed

• Variables left out of env, such as tokens, no longer reach the child (#48)
  • Fixes #47

[0.4.11] - 2026-09-30

Added

• Native Windows ARM64 support (#46)
  • Ship a pre-built rust_pty_arm64.dll (built on GitHub's windows-11-arm runner for aarch64-pc-windows-msvc) alongside the existing x64 rust_pty.dll, whose filename is unchanged
  • Link the MSVC runtime statically (-C target-feature=+crt-static) to avoid a Visual C++ Redistributable dependency
  • Select the ARM64 DLL at runtime and in the bun build --compile embed path, falling back to rust_pty.dll
  • Move native library filename resolution into src/library.ts with unit tests
  • Add a windows-11-arm job to the test matrix that runs the unit and integration tests against the exact ARM64 artifact

• 14ac2ca chore: release v0.5.1
• c55cf57 fix: leave test files out of the npm package (#50)
• a3135e4 chore: release v0.5.0
• 46dfb4e fix: build the child environment as node-pty does on Unix (#49)
• 5d12222 fix: replace the child environment with the supplied env map (#48)
• a582ae1 chore: release v0.4.11
• c5f5060 feat: add native Windows ARM64 support (#46)
• See full diff in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)