Open
Conversation
The Wasmtime API changes in incompatible ways between major releases, which occur approximately once per month. The DevBuild option downloads the latest development release of Wasmtime, which often does not work with the main or release branches. Disable DevBuild to default to the target version of Wasmtime.
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.
It's very confusing when the main branch and even the release branches do not work (pass tests) without changing the DevBuild setting. It should be disabled by default, and only enabled by those wishing to work on synchronizing wasmtime-dotnet with the dev branch of Wasmtime.
Fixes #357