debug@2.5.0 breaks build 🚨 #101
Open
Conversation
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
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.
Hello lovely humans,
debug just published its new version 2.5.0.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As debug is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
The new version differs by 107 commits .
355e327release 2.5.0d85c0c6build perf, fix for bowerfile, fix for webworkerdc043cfMerge pull request #378 from yamikuronue/replace-babel-with-browserifyf512cf2Merge remote-tracking branch 'upstream/master' into replace-babel-with-browserifyf098331Merge pull request #388 from ForsakenHarmony/patch-1a16cf42Merge pull request #387 from kribblo/patch-178e31a8Update browser.js408ae94Use typeof window.process !== 'undefined'f484cfefix merge errors23af483Merge remote-tracking branch 'upstream/master' into replace-babel-with-browserify3e1a15dfix: merged again, because it didn't take. Guess I did it wrong?67182fdfix: Whoops, didn't merge the tests properly. Resolved.2a01c6cMerged from upstream/master. I left the dist/debug in place because my hook now updates it automatically, but I removed the babelrc file since we don't need it anymore.6e934e9Fix for #381. Moved .babelrc into test folder, where it is used and which is not built with the module. (#383)6a8d525chore: add coverallsThere are 107 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade