coveralls@2.11.11 breaks build 🚨 #36
Merged
Conversation
This file contains 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
7rulnik
force-pushed
the
greenkeeper-coveralls-2.11.11
branch
4 times, most recently
from
88798c7
to
e77175e
Compare
|
Changes Unknown when pulling e77175e on greenkeeper-coveralls-2.11.11 into * on master*. |
|
Changes Unknown when pulling e77175e on greenkeeper-coveralls-2.11.11 into * on master*. |
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,
coveralls just published its new version 2.11.11.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As coveralls 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 💪
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 8 commits .
55ebe27version bump57db719Merge pull request #125 from Joe8Bit/chore_bump-request-version49d8626Merge pull request #123 from teppeis/patch-1742efbbBumprequestNPM module to fix security issue586bbd9version bump01e6fb9Merge pull request #124 from tparnell8/appveyor59356d4add appveyor support60fb2d1Delete npm-debug.logSee the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade