[email protected] breaks build 🚨 #49
Open
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
cybertk
force-pushed
the
greenkeeper-time-grunt-1.4.0
branch
2 times, most recently
from
05b830e to
9a3475e
Compare
cybertk
force-pushed
the
greenkeeper-time-grunt-1.4.0
branch
from
9a3475e to
5f9b6a5
Compare
cybertk
force-pushed
the
greenkeeper-time-grunt-1.4.0
branch
2 times, most recently
from
4956ca7 to
2b99c00
Compare
1 similar comment
cybertk
force-pushed
the
greenkeeper-time-grunt-1.4.0
branch
from
2b99c00 to
c4b3a25
Compare
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,
time-grunt just published its new version 1.4.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 time-grunt 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 15 commits .
29dc47d1.4.0ce3b96fupdate screenshot9f42505display local time instead of UTC time (#83)3c67154Override xo/no-process-exit3ee8b23Update .travis.ymlcbbabe0Merge pull request #79 from sindresorhus/adrianlee44/fix-negatived72863emeta tweaks2029b20Merge pull request #75 from ntwb/patch-193a1d44Travis CI: Test on Node.js v4.x.x and v5.x.xdb11c161.3.01472581minor tweakse5b74e5Close #73 PR: Ignore watch task. Fixes #51.e16bf951.2.2b42b4e7Merge pull request #70 from dominykas/patch-1efbee3aBumping pretty-ms to 2.xSee the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade