Skip to content

Update the wasm-tools family of crates to version 249#13389

Open
fitzgen wants to merge 3 commits into
bytecodealliance:mainfrom
fitzgen:update-wasm-tools-to-249
Open

Update the wasm-tools family of crates to version 249#13389
fitzgen wants to merge 3 commits into
bytecodealliance:mainfrom
fitzgen:update-wasm-tools-to-249

Conversation

@fitzgen
Copy link
Copy Markdown
Member

@fitzgen fitzgen commented May 15, 2026

Fixes #11427

@fitzgen fitzgen requested review from a team as code owners May 15, 2026 17:55
@fitzgen fitzgen requested review from alexcrichton and pchickey and removed request for a team May 15, 2026 17:55
@github-actions github-actions Bot added wasmtime:api Related to the API of the `wasmtime` crate itself wizer Issues related to Wizer snapshotting, pre-initialization, and the `wasmtime wizer` subcommand labels May 15, 2026
@github-actions
Copy link
Copy Markdown

Subscribe to Label Action

cc @fitzgen

Details This issue or pull request has been labeled: "wasmtime:api", "wizer"

Thus the following users have been cc'd because of the following labels:

  • fitzgen: wizer

To subscribe or unsubscribe from this label, edit the .github/subscribe-to-label.json configuration file.

Learn more.

@fitzgen
Copy link
Copy Markdown
Member Author

fitzgen commented May 15, 2026

(Larger set of test updates required for this one, still working on it; looks like I might need to upstream so CM test fixes as well.)

@alexcrichton
Copy link
Copy Markdown
Member

Feel free to temporarily exclude tests for upstream component model tests, I can get around to those later.

@fitzgen
Copy link
Copy Markdown
Member Author

fitzgen commented May 16, 2026

Depends on WebAssembly/component-model#652

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

wasmtime:api Related to the API of the `wasmtime` crate itself wizer Issues related to Wizer snapshotting, pre-initialization, and the `wasmtime wizer` subcommand

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Huge array allocations are timing out during fuzzing

2 participants