-
-
Notifications
You must be signed in to change notification settings - Fork 621
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): pin dependencies #711
Conversation
@dhruvdutt The most important CI builds failed. This way your PR can't be merged. Please take a look at the CI results from travis (failure) and fix these issues. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is still in discussion, so this is up for chills
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm
There's a failing test... Does that mean that pinning the dependencies caused a different behaviour of the library? That's odd. We should fix it |
It's from uglify/terser test, which PR changed that again? Was recently done |
There's an open PR |
If it doesnt fail at that then merging that would be nice |
Seems like this is a side effect of something. Pinning dependencies wouldn't change anything. |
Let’s do this properly Dhruvdut... |
Some weird issue. It worked locally for me. Looking into it. |
What kind of change does this PR introduce?
Dependencies pinning
Did you add tests for your changes?
N/A
If relevant, did you update the documentation?
N/A
Summary
Does this PR introduce a breaking change?
No
Other information
Fixes #697