alexcrichton commented on Issue #2481:
I believe the failures here are for wasmparser to fix -- https://github.com/bytecodealliance/wasm-tools/pull/164
alexcrichton commented on Issue #2481:
Ok I've published 0.69.2
abrown commented on Issue #2481:
@alexcrichton, @fitzgen: I went with
0.69in theCargo.tomlfiles and locked it to0.69.2in theCargo.lock--is that the right choice?Also, if we update
objectto use wasmparser's0.69then we would have the same version ofwasmparserused everywhere in the project. Right nowobjectis still looking back at0.57.
alexcrichton commented on Issue #2481:
Ideally one lock file would mentione 0.69.2 to indicate that we require at least that version, but otherwise seems fine!
alexcrichton edited a comment on Issue #2481:
Ideally one
lockmanifest file would mentione 0.69.2 to indicate that we require at least that version, but otherwise seems fine!
fitzgen commented on Issue #2481:
I personally prefer to update the
.tomlto the minor version, just so that I don't have to do different things depending on if I'm in a project that has a committed lock file or not.It would be nice to update
objectso that we only have one copy ofwasmparserbut seems orthogonal to this work.
github-actions[bot] commented on Issue #2481:
Subscribe to Label Action
cc @fitzgen, @peterhuene
<details>
This issue or pull request has been labeled: "cranelift", "cranelift:wasm", "fuzzing", "lightbeam", "wasmtime:api"Thus the following users have been cc'd because of the following labels:
- fitzgen: fuzzing
- peterhuene: wasmtime:api
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
Last updated: Dec 06 2025 at 06:05 UTC