-
Notifications
You must be signed in to change notification settings - Fork 10
An in-range update of eslint-plugin-flowtype is breaking the build 🚨 #125
Comments
Version 2.31.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.31.0<a name"2.31.0"> 2.31.0 (2017-04-18)Features |
Version 2.32.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.32.0<a name"2.32.0"> 2.32.0 (2017-04-19)Features |
Version 2.32.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.32.1<a name"2.32.1"> 2.32.1 (2017-04-19)Bug Fixes
|
Version 2.33.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.33.0<a name"2.33.0"> 2.33.0 (2017-05-14)FeaturesCommitsThe new version differs by 4 commits0.
false See the full diff |
Version 2.34.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.34.0<a name"2.34.0"> 2.34.0 (2017-05-30)FeaturesCommitsThe new version differs by 6 commits.
See the full diff |
Version 2.34.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv2.34.1<a name"2.34.1"> 2.34.1 (2017-06-28)Bug FixesCommitsThe new version differs by 7 commits.
See the full diff |
Version 2.35.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv2.35.0<a name"2.35.0"> 2.35.0 (2017-07-11)Bug Fixes
Features |
Version 2.35.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv2.35.1<a name"2.35.1"> 2.35.1 (2017-09-01)Bug Fixes |
Version 2.30.4 of eslint-plugin-flowtype just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As eslint-plugin-flowtype 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
❌ coverage/coveralls Coverage pending from Coveralls.io Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
v2.30.4<a name"2.30.4">
2.30.4 (2017-03-21)
Bug Fixes
Commits
The new version differs by 1 commits .
636cead
fix: no-dupe-keys with legal duplicated keys (#148)
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: