Repository navigation
chore(release): prepare v0.20.0 - #2775
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
bashkit | 332ac97 | Commit Preview URL Branch Preview URL |
Oct 25 2026, 12:03 AM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Prepare Bashkit 0.20.0 across Rust, Python, native npm, browser npm, CLI and C ABI artifacts. Synchronize version pins and standalone lockfiles; update dependency examples and release notes. Regenerated Python/TypeScript references have no drift.
Highlights: live command I/O/async sinks; embedded Python/TypeScript host callbacks; optional runtime warm-up; Wasmtime 48.0.7, patched TLS/crypto/Tokio and Node build/runtime guidance.
Why
Ship the security fixes and new APIs since 0.19.0. A minor release reflects the Rust analysis API rename:
analysis::CommandContext→CommandPlacement.AnalyzedCommand.contextkeeps its serialized name/values; rootCommandContextnow means the live invocation context.Before / After
Preflight registry baseline: 0.19.0. Local packaged 0.20.0 consumer evidence:
Publish-readiness:
just pre-pr: 7,259 Rust tests, script/docs/workflow checks and cargo-vet passed.cargo clippy --locked --all-targets --all-features -- -D warnings: passed.cargo publish --dry-run --allow-dirty: verifiedbashkit-cpython-wasm,bashkit,bashkit-cli,bashkit-scripted-tool0.20.0 together.--locked.just check-nightly: last three nightly and fuzz runs all green; exact final-head nightly40145150204passed Audit, Security Analysis, Miri and AddressSanitizer.Risk
CommandPlacement.atomic-polyfillremains unmaintained. Node 18/20 compatibility is not security support. Downstream Rust lockfiles still need refresh/rebuild.Checklist
332ac9778c9c07e63724eab493406b4f59e8d936)After merge: verify immutable tag/source, all four crates, PyPI wheels/sdist, both npm latest tags and archive integrity, CLI/C ABI platform archives/checksums, Homebrew formula, and public consumer smoke. Starting workflows is not completion.