Bumping version of wasi crate dependency

0.12.0 suffered from a bug the could impact users using lower versions
of wit-bindgen dependencies. Mixed versions of wit-bindgen generated
bindings in a single project would cause a symbol collision. This is
fixed by newer versions of wit-bindgen and wasi 0.12.1 contains bindings
generated by one of these newer versions. See issue below for details:
bytecodealliance/wit-bindgen#849

Update CHANGELOG

CHANGELOG.next.toml

@@ -19,7 +19,7 @@ author = "jackkleeman"
 
 [[smithy-rs]]
 message = "Added aws-smithy-wasm crate to enable SDK use in WASI compliant environments"
-references = ["smithy-rs#2087", "smithy-rs#2520", "smithy-rs#3409", "aws-sdk-rust#59"]
+references = ["smithy-rs#2087", "smithy-rs#2520", "smithy-rs#3409", "aws-sdk-rust#59", "smithy-rs#3476"]
 meta = { "breaking" = false, "tada" = true, "bug" = false }
 authors = ["landonxjames", "eduardomourar"]
 

rust-runtime/aws-smithy-wasm/Cargo.toml

@@ -19,7 +19,7 @@ http = "1.0.0"
 tracing = "0.1.40"
 # Note the wasi crate will only build for target wasm32-wasi, but having a target
 # statement here breaks some of the CI tests, so we leave it with the rest of the deps
-wasi = "0.12.0" # This is build on wasi-0.2.0
+wasi = "0.12.1" # This is build on wasi-0.2.0
 
 [package.metadata.docs.rs]
 all-features = true