Highlights

• The native npm package ships again. @everruns/bashkit stalled at 0.16.0 during the v0.17.0 release because the publish workflow tested Node 20 in ways CI no longer did; the release path and CI now agree, and a check fails when they drift apart again.

Fixed

• The npm native package publishes again: publish-js.yml no longer runs the ava suites on Node 20, which ava 8 dropped support for. Node 20 keeps running the runtime-compat suite against the shipped binding, matching how js.yml already split them; that suite runs under bash so the Windows runner expands its glob, which Node 20 cannot do itself.
• The JS runtime-compat mount and unmount test mounts a real temporary directory instead of a hardcoded /tmp, so it passes on the Windows runners the release workflow tests on.

Added

• just check-workflow-parity fails when a release workflow tests a runtime version CI does not, when a shared test suite is gated to more versions at release time than in CI, or when dtolnay/rust-toolchain pins disagree across workflows. This class of drift is otherwise invisible until a tag exists and part of the release has already published.

Performance

• Ported coreutils builtins reuse pre-built clap Command definitions instead of rebuilding them per invocation (#2347).

What's Changed

• perf(builtins): cache pre-built clap Commands for ported coreutils builtins (#2347) by @chaliy
• fix(test): mount a real temp dir in the JS runtime-compat suite (#2346) by @chaliy
• fix(release): run the Node 20 compat suite under bash on Windows (#2345) by @chaliy
• fix(release): unblock the npm native publish and catch release/CI matrix drift (#2344) by @chaliy

Full Changelog: https://github.com/everruns/bashkit/compare/v0.17.0...v0.17.1