Repository navigation
chore(release): prepare v0.20.2 - #2800
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
bashkit | 488af11 | Commit Preview URL Branch Preview URL |
Oct 30 2026, 09:21 PM |
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.2 from current main, including Wasmtime 48.0.8 (#2798), Authenticode-signed Windows Python wheels (#2799), binary-safe HTTP output (#2778), and recursive directory-dot copies (#2796). Synchronize Rust/npm versions, internal Rust dependency requirements, auxiliary lockfiles, and documentation examples; record all 20 merged changes since 0.20.1.
Why
Downstream applications need a published Bashkit and bashkit-cpython-wasm pair built with the patched Wasmtime engine. Include the latest merged Windows signing changes in the same release.
Before / After
Before: all four Rust packages, PyPI, and both npm packages publish 0.20.1. The published CPython runtime predates the Wasmtime 48.0.8 fix.
After: release automation will publish 0.20.2, with both the CPython build dependency and runtime using
=48.0.8. The four-package Cargo dry-run verified the exact unpublished internal dependency graph. Native JS smoke confirmedcp -r source/. destinationcopies contents without an extra directory layer.Publish readiness
just pre-pr: passed; 7,274 Rust tests plus 204 script tests (four platform-specific skips).cargo clippy --all-targets --all-features -- -D warnings: passed.just test: passed, including 19 security failpoint tests.cargo vet --locked: passed using the existing audit policy.cargo publish --dry-run --allow-dirty: passed.cargo package -p bashkit-cpython-wasm --allow-dirty: 8,159,908 bytes, below the 10 MiB registry limit.cargo metadata --locked --offline: passed; Wasmtime resolves to 48.0.8.sha256:170798025f72b9dfe4d0ff5852043c5e50dd8c2271a529019a38b5aec80a5fb8.Local differential tests used pinned jq 1.8.1/ripgrep 15.1.0 and an isolated temporary directory: the sandbox's synthetic
/tmp/.gitotherwise changes the real-ripgrep oracle's repository detection. Assertions and security policy were unchanged.just check-nightlypassed: the last three nightly and last three fuzz runs are green. Fresh full validation on the release base:Risk
Medium: release fan-out spans Rust, Python, npm, CLI/Homebrew, and C ABI archives. Windows signing is now mandatory for the PyPI publication path; its production smoke passed. Monitor all publication workflows and verify registries after merge.
Checklist