Wasmtime GitHub notifications bot (Aug 23 2025 at 18:05): Wasmtime GitHub notifications bot (Aug 23 2025 at 18:05):badeend opened PR #11517 from badeend:fallible-constructors to bytecodealliance:main:
That version comes with support for fallible resource constructors.
wasmtime-wit-bindgendoesn't need any additional changes to support this, though I've added a codegen test for it to be sure.
Wasmtime GitHub notifications bot (Aug 23 2025 at 18:05):badeend requested wasmtime-default-reviewers for a review on PR #11517.
Wasmtime GitHub notifications bot (Aug 23 2025 at 18:05):badeend requested dicej for a review on PR #11517.
Wasmtime GitHub notifications bot (Aug 23 2025 at 18:05):badeend requested wasmtime-core-reviewers for a review on PR #11517.
Wasmtime GitHub notifications bot (Aug 25 2025 at 13:18):dicej submitted PR review.
Wasmtime GitHub notifications bot (Aug 25 2025 at 13:42):@alexcrichton Do you happen to know why these updates aren't covered by the wildcard audits in
supply-chain/audits.toml?
Wasmtime GitHub notifications bot (Aug 25 2025 at 13:54):@alexcrichton Do you happen to know why these updates aren't covered by the wildcard audits in
supply-chain/audits.toml?
cargo vetclaims the publisher isUNKNOWN, which may be the reason. Not sure why that would happen, though.
Wasmtime GitHub notifications bot (Aug 25 2025 at 14:28):alexcrichton updated PR #11517.
Wasmtime GitHub notifications bot (Aug 25 2025 at 14:29):alexcrichton commented on PR #11517:
I think the problem is due to the fact of wasm-tools now using crates.io trusted publishing workflows. I've added audits in the meantime.
Wasmtime GitHub notifications bot (Aug 25 2025 at 14:29):alexcrichton has enabled auto merge for PR #11517.
Wasmtime GitHub notifications bot (Aug 25 2025 at 17:25):badeend commented on PR #11517:
There were connectivity issues during the CI run. Maybe try again?
Wasmtime GitHub notifications bot (Aug 25 2025 at 20:11):dicej merged PR #11517.
Last updated: Dec 06 2025 at 07:03 UTC