Fix cdn build to use super-three 0.184.0#5826
Merged
Merged
Conversation
Contributor
Author
|
Ah the a-frobot actually doesn't check for package-lock.json to trigger a build. I added that to the new pending Github CI. |
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.
The a-frobot built the cdn build still with 0.181.0, we also got the error downloading super-three 0.184.0 in the tests ec6f6a8#commitcomment-188253469
Also the package-lock.json wasn't pushed with the correct super-three version so here it is, it should triggers a correct new build.
Separate note, we should switch to Github CI for the build #5813