Update to wasm_runtime_layer v0.6 (breaking)#28
Open
T0mstone wants to merge 4 commits into
Open
Conversation
...because apparently the version 0.6.0 published to crates.io is just broken
T0mstone
changed the title
wasm_runtime_layer v0.6 (breaking)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I added some new
'staticbounds to matchwasm_runtime_layer, which is obviously a breaking change, so I also increased the version to0.2.0.Also, I removed the
>=from thewasm_runtime_layerdependency, since we already saw what happened due to that (#25).Also also: Apparently the version 0.6 of
wasm_runtime_layeron crates.io is broken, so I patched it to the current main in theCargo.toml. This means that this PR is blocked on the next version ofwasm_runtime_layerbeing released, whereafter that patch can be removed.