Wasmtime GitHub notifications bot (Jan 29 2026 at 15:48): Wasmtime GitHub notifications bot (Jan 29 2026 at 15:48):TartanLlama opened PR #12466 from TartanLlama:sy/component-model-threading-v2 to bytecodealliance:main:
A draft PR for upcoming proposed changes to the component model threading intrinsics to support the wasi-libc pthreads implementation.
Wasmtime GitHub notifications bot (Jan 29 2026 at 15:48):TartanLlama requested wasmtime-compiler-reviewers for a review on PR #12466.
Wasmtime GitHub notifications bot (Jan 29 2026 at 15:48):TartanLlama requested fitzgen for a review on PR #12466.
Wasmtime GitHub notifications bot (Jan 29 2026 at 15:48):TartanLlama requested wasmtime-core-reviewers for a review on PR #12466.
Wasmtime GitHub notifications bot (Jan 29 2026 at 15:48):TartanLlama converted PR #12466 Component model threading intrinsic updates to a draft.
Wasmtime GitHub notifications bot (Jan 29 2026 at 16:58):github-actions[bot] added the label wasmtime:config on PR #12466.
Wasmtime GitHub notifications bot (Jan 29 2026 at 16:58):github-actions[bot] added the label wasmtime:api on PR #12466.
Wasmtime GitHub notifications bot (Jan 29 2026 at 17:56):github-actions[bot] commented on PR #12466:
Label Messager: wasmtime:config
It looks like you are changing Wasmtime's configuration options. Make sure to
complete this check list:
[ ] If you added a new
Configmethod, you wrote extensive documentation for
it.<details>
Our documentation should be of the following form:
```text
Short, simple summary sentence.More details. These details can be multiple paragraphs. There should be
information about not just the method, but its parameters and results as
well.Is this method fallible? If so, when can it return an error?
Can this method panic? If so, when does it panic?
Example
Optional example here.
```</details>
[ ] If you added a new
Configmethod, or modified an existing one, you
ensured that this configuration is exercised by the fuzz targets.<details>
For example, if you expose a new strategy for allocating the next instance
slot inside the pooling allocator, you should ensure that at least one of our
fuzz targets exercises that new strategy.Often, all that is required of you is to ensure that there is a knob for this
configuration option in [wasmtime_fuzzing::Config][fuzzing-config] (or one
of its nestedstructs).Rarely, this may require authoring a new fuzz target to specifically test this
configuration. See [our docs on fuzzing][fuzzing-docs] for more details.</details>
[ ] 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.[fuzzing-config]: https://github.com/bytecodealliance/wasmtime/blob/ca0e8d0a1d8cefc0496dba2f77a670571d8fdcab/crates/fuzzing/src/generators.rs#L182-L194
[fuzzing-docs]: https://docs.wasmtime.dev/contributing-fuzzing.html
<details>
To modify this label's message, edit the <code>.github/label-messager/wasmtime-config.md</code> file.
To add new label messages or remove existing label messages, edit the
<code>.github/label-messager.json</code> configuration file.</details>
Wasmtime GitHub notifications bot (Feb 12 2026 at 16:03):alexcrichton closed without merge PR #12466.
Last updated: Feb 24 2026 at 04:36 UTC