Open alexcrichton opened 5 days ago
I'll note that this is a draft as I'd like to get in https://github.com/bytecodealliance/wit-bindgen/pull/990 and https://github.com/bytecodealliance/wit-bindgen/pull/989 and update wit-bindgen here too
Ok should be reading pending CI
On second thought let's not update wit-bindgen.
It looks like you are changing Wasmtime's configuration options. Make sure to complete this check list:
[ ] If you added a new Config
method, you wrote extensive documentation for
it.
[ ] If you added a new Config
method, or modified an existing one, you
ensured that this configuration is exercised by the fuzz targets.
[ ] If you are enabling a configuration option by default, make sure that it has been fuzzed for at least two weeks before turning it on by default.
.github/label-messager/wasmtime-config.md
file.
To add new label messages or remove existing label messages, edit the
.github/label-messager.json
configuration file.
[Learn more.](https://github.com/bytecodealliance/label-messager-action)
This notably brings in a limitation where component model flags types must have 32 or fewer flags in accordance with the transition plan of https://github.com/WebAssembly/component-model/issues/370. A feature flag is added to go back to the previous behavior to avoid breaking anyone too much.
This additionally brings in a fix for a panic when validating invalid modules with tail calls.