Bump Wasmtime to 20.0.0 #8046
Merged
Bump Wasmtime to 20.0.0 #8046
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
wasmtime-publish
requested review from
cfallin and
fitzgen
and removed request for
a team
alexcrichton
approved these changes
Mar 5, 2024
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 is an automated pull request from CI which indicates that the next
release-19.0.0branch has been created and themainbranch is getting its version number bumped from 19.0.0 to 20.0.0.Maintainers should take a moment to review the release notes for 19.0.0, and if any changes are necessary send PRs to the
mainbranch to update RELEASES.md and then backport these PRs to the release branch.Maintainers should also review that aarch64-apple-darwin builds are passing via embark's CI.
Another automated PR will be made in roughly 2 weeks time when for the actual release itself.
If any issues arise on the
mainbranch before the release is made then the issue should first be fixed onmainand then backport to therelease-19.0.0branch.