Open greenkeeper[bot] opened 7 years ago
After pinning to 8.0.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Your tests are still failing with this version. Compare the changes π¨
The new version differs by 8 commits ahead by 8, behind by 1.
a0fbd50
8.0.2
2004b91
require correct deps
fa56d21
Always use unpad (#535)
295091d
Allow ^ version for babel dependencies (#534)
d3b8519
fix(package): update babylon to version 7.0.0-beta.31 (#533)
54ab4ac
8.0.1
c1a7882
Update README.md support (#531) [skip ci]
51100c9
chore(package): update mocha to version 4.0.0 (#524)
See the full diff
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Use ESLint's API to customize scope analysis and avoid monkeypatching: #542
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
The new version differs by 11 commits.
2bd8508
8.2.4
5881648
Add test for template string with object with template string inside (#639)
476426a
Support OptionalMemberExpression with scope too (#634)
92874d4
Drop node4 in travis
d2ac299
Bump Babel deps
e63962d
refactor: rename babylon to @babel/parser
873f02f
Fix converting template types to handle nested templates (#610)
74a3207
Fix token types for experimental operators (#632)
e802577
Add support for the optional chaining operator (#630)
ebc46e1
don't require unpad per test fixture, fixes #572 (#618)
9641e4b
updates readme for latest eslint & babel-eslint (#607) [skip ci]
See the full diff
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Version 8.0.1 of babel-eslint just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As babel-eslint 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 :muscle:
Status Details
- β **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/Kronos-JMF/jmf-graphql/builds/280201672?utm_source=github_status&utm_medium=notification)Release Notes
v8.0.1v8.0.1
Handle optionalCatchBinding: #521
Commits
The new version differs by 2 commits.
6c7e3d0
8.0.1
5742b71
Adding optionalCatchBinding to plugins. (#521)
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: