-
Notifications
You must be signed in to change notification settings - Fork 25
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
An in-range update of browserify is breaking the build 🚨 #49
Labels
Comments
Version 14.5.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 24 commits.
There are 24 commits in total. See the full diff |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version 14.2.0 of browserify just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As browserify is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
Commits
The new version differs by 5 commits .
18e1d65
14.2.0
0e1a7a0
add cli support for --transform-key to support mode's like production/staging/etc..
a5aa660
Merge pull request #1701 from wogsland/doc-fix
ae281bc
Fixed documentation formatting that was bugging me
fe8c57b
async test for node 7
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: