Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bump Wasmtime version to 5.0.1 #1243

Merged
merged 1 commit into from
Mar 8, 2023
Merged

bump Wasmtime version to 5.0.1 #1243

merged 1 commit into from
Mar 8, 2023

Conversation

dicej
Copy link
Contributor

@dicej dicej commented Mar 8, 2023

No description provided.

Signed-off-by: Joel Dice <joel.dice@fermyon.com>
@lann
Copy link
Collaborator

lann commented Mar 8, 2023

I assume this doesn't require bumping wit-bindgen-backport? It makes sense that it wouldn't necessarily.

@dicej
Copy link
Contributor Author

dicej commented Mar 8, 2023

I assume this doesn't require bumping wit-bindgen-backport? It makes sense that it wouldn't necessarily.

The same thing occurred to me, but I think we're good, both from a semver perspective and a security perspective, given that we're pulling in the right versions of everything in Cargo.lock.

@dicej dicej merged commit 492a947 into fermyon:main Mar 8, 2023
@dicej dicej deleted the wasmtime-5.0.1 branch March 8, 2023 20:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants