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

chore: update wasmtime to 1.0 #963

Merged
merged 1 commit into from
Oct 13, 2022
Merged

Conversation

Stebalien
Copy link
Member

Backports #943 without the other dependency updates.

Fixes #962.

Backports #943 without the other dependency updates.

Fixes #962.
@Stebalien
Copy link
Member Author

See the linked issue for why. My plan is to:

  1. Cut a 2.1.0 release with this change.
  2. Include that in the next feature release.

I just cut a 2.0.0 release so users would be able to decide if/when they pull this update in.

@codecov-commenter
Copy link

codecov-commenter commented Oct 13, 2022

Codecov Report

Merging #963 (82c2f7c) into release/v2 (98cc814) will decrease coverage by 0.20%.
The diff coverage is 100.00%.

Additional details and impacted files

Impacted file tree graph

@@              Coverage Diff               @@
##           release/v2     #963      +/-   ##
==============================================
- Coverage       51.94%   51.74%   -0.21%     
==============================================
  Files             124      124              
  Lines           10095    10139      +44     
==============================================
+ Hits             5244     5246       +2     
- Misses           4851     4893      +42     
Impacted Files Coverage Δ
fvm/src/machine/engine.rs 34.79% <100.00%> (-5.29%) ⬇️

@Stebalien Stebalien merged commit 9567291 into release/v2 Oct 13, 2022
@Stebalien Stebalien deleted the chore/v2-update-wasmtime branch October 13, 2022 04:39
This was referenced Oct 14, 2022
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.

3 participants