chore(release): prepare v0.17.1

[chaliy]

What changed

Patch release carrying the three fixes merged since v0.17.0 (#2344, #2345, #2346) and putting @everruns/bashkit back on npm latest.

Why

v0.17.0 published to crates.io, PyPI, and @everruns/bashkit-wasm, but the native npm package stalled at 0.16.0: publish-js.yml ran the ava suites on Node 20 after ava 8 dropped support, then (once gated) hit two more Windows-only faults — a glob Node 20 cannot expand under PowerShell, and a runtime-compat test mounting a hardcoded host /tmp.

With those fixed, a manual dispatch of publish-js.yml from main published 0.17.0 to npm under the next dist-tag, not latest. That is the workflow behaving correctly: only a run whose ref is refs/tags/vX.Y.Z may publish latest, so branch and manual refs cannot become the default install target. The v0.17.0 tag predates the fixes, so re-dispatching from that tag would just fail again. Cutting v0.17.1 is the way to get a tag that both contains the fixes and publishes latest.

Also records that dist-tag rule in knowledge/operations/release-process.md, so a failed npm publish is not chased with another dispatch from main.

Before / After

Registries now:

crates.io bashkit / bashkit-cli -> 0.17.0
PyPI bashkit -> 0.17.0
npm @everruns/bashkit-wasm (latest) -> 0.17.0
npm @everruns/bashkit (latest) -> 0.16.0 (0.17.0 sits on `next`)

After this release all six report 0.17.1, including npm native on latest.

Publish-readiness:

• just pre-pr passed: fmt, clippy, Rust test suite, script unit tests, capability parity, OKF bundle, doc links, just check-workflow-parity, cargo vet.
• cargo publish --dry-run -p bashkit packaged and verified v0.17.1.
• Registry-backed bashkit-cli package dry-run succeeded (7 files, 229.6 KiB). The proxy now reports kept http_client, ring, git, jq, tzdata; dropped (none) — the published 0.17.0 core carries the features that broke it during the last release, confirming the chore(release): prepare v0.17.0 #2343 fix generalizes.
• Version sync verified across workspace Cargo.toml, the CLI path-dep pin, both package.json files, crates/bashkit/src/lib.rs, README, docs snippets, and all four lockfiles.
• No API surface changed since v0.17.0 (workflow, test, and tooling only), so the self-hosted API references are untouched; apidocs-drift still covers them.

Risk

• Low
• No library code changes since v0.17.0; the diff is a version bump plus changelog and knowledge.
• npm native latest moves 0.16.0 → 0.17.1, skipping 0.17.0, which remains installable on next.

Checklist

• Tests added or updated
• Backward compatibility considered

[cloudflare-workers-and-pages]

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	bashkit	600a28e	Commit Preview URL Branch Preview URL	Aug 22 2026, 07:46 PM