Bumping version of wasi
crate dependency
#3476
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
The
0.12.0
version ofwasi
suffered from a bug the could impact users using lower versions ofwit-bindgen
dependencies. Mixed versions ofwit-bindgen
generated bindings in a single project would cause a symbol collision. This is fixed by newer versions ofwit-bindgen
andwasi = 0.12.1
contains bindings generated by one of these newer versions. See this issue for details: bytecodealliance/wit-bindgen#849 and a longer discussion of the issue on Zulip here.Description
Bumped version of
wasi
dependency inaws-amithy-wasm
from0.12.0
->0.12.1
Testing
Checklist
CHANGELOG.next.toml
if I made changes to the smithy-rs codegen or runtime cratesBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.