Skip to content

cargo: pin wasmtime-environ and wit-parser once, in the workspace table - #274

Merged
lannbot merged 1 commit into
mainfrom
workspace-deps
Sep 4, 2026
Merged

cargo: pin wasmtime-environ and wit-parser once, in the workspace table#274
lannbot merged 1 commit into
mainfrom
workspace-deps

Conversation

@lannbot

@lannbot lannbot commented Sep 4, 2026

Copy link
Copy Markdown
Collaborator

The wasmtime-environ =47.0.3 (translator-shim) and wit-parser =0.252.0 (bindgen) pins must move together but were joined only by a "bump together" comment in each manifest. Both now come from [workspace.dependencies] in the root Cargo.toml; the crates use { workspace = true }.

just test-rust gains a drift check: fails if wasmparser, wit-parser or wasm-encoder resolve to more than one version across translator-shim + bindgen. testgen is excluded (uses wast 255 deliberately, per the architecture.md risk table).

Considered and rejected: routing both through the wasmtime crate's re-exports (reexport-wasmparser, wit-parser). wasmtime::component::wit_parser requires the runtime feature, which on the shim's wasm32-unknown-unknown cdylib needs the custom-platform features plus stub wasmtime_mprotect/munmap/page_size/tls_get symbols to link, and adds ~19 crates — for an engine the shim never runs.

Gates: cargo build --workspace, wasm32 release build of the shim, just test-rust, just version-guard-local — all pass. Cargo.lock unchanged. Automerge armed.

The two pins must move together (wasmtime 47 links wasmparser 0.252;
wit-parser 0.252 is the same wasm-tools release) but lived in two crate
manifests joined only by a comment. Both now come from
[workspace.dependencies], and `just test-rust` fails if wasmparser,
wit-parser or wasm-encoder resolve to more than one version across
translator-shim + bindgen (testgen excluded: it uses wast 255 on purpose).
@lannbot
lannbot enabled auto-merge September 4, 2026 21:00
@lannbot
lannbot merged commit 4452e74 into main Sep 4, 2026
3 checks passed
@lannbot
lannbot deleted the workspace-deps branch September 4, 2026 21:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants