Unbreak WABT again by using main instead of a commit#6614
Merged
Conversation
Member
|
Ugh, who force-pushes to main/master?! |
alexreinking
approved these changes
Feb 14, 2022
alexreinking
left a comment
alexreinking
left a comment
Member
There was a problem hiding this comment.
Still wish this were a cache variable, but I guess this is just a sharp edge no matter what until WABT tags a release
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
2 participants
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.
Commit 09c40635207d42dd30ffaca22477fd3491dd9e7d is no longer being recognized for WABT; rather than whack-a-mole, let's just use
maintemporarily (I've requested the WABT team make a new tag ASAP so we can standardize on the new API)