chore: release v3.11.1 #2065
Merged
chore: release v3.11.1 #2065
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release/v3 #2065 +/- ##
===========================================
Coverage 68.57% 68.57%
===========================================
Files 96 96
Lines 8694 8694
===========================================
Hits 5962 5962
Misses 2732 2732 |
This release brings in wasmtime 25.0.2. We're doing this as a patch release because 3.11 brought in wasmtime 24 which introduced a significant regression in wasm compile time (and there shouldn't be anything breaking in this release either).
Stebalien
force-pushed
the
steb/release-v3
branch
from
e25c5dd
to
79c3c13
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This release brings in wasmtime 25.0.2. We're doing this as a patch release because 3.11 brought in wasmtime 24 which introduced a significant regression in wasm compile time (and there shouldn't be anything breaking in this release either).