Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of babel-eslint is breaking the build 🚨 #1153

Closed
greenkeeper bot opened this issue Jun 22, 2018 · 4 comments

Comments

@greenkeeper
Copy link
Contributor

commented Jun 22, 2018

Version 8.2.4 of babel-eslint was just published.

Branch Build failing 🚨
Dependency [babel-eslint](https://github.com/babel/babel-eslint)
Current Version 8.2.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

babel-eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

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

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper greenkeeper bot added the greenkeeper label Jun 22, 2018

@greenkeeper

This comment has been minimized.

Copy link
Contributor Author

commented Jun 22, 2018

After pinning to 8.2.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

@greenkeeper

This comment has been minimized.

Copy link
Contributor Author

commented Jun 23, 2018

Version 8.2.5 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 2 commits.

See the full diff

@greenkeeper

This comment has been minimized.

Copy link
Contributor Author

commented Jul 12, 2018

Version 8.2.6 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 2 commits.

See the full diff

@stale

This comment has been minimized.

Copy link

commented Oct 10, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label Oct 10, 2018

@stale stale bot closed this Oct 17, 2018

@lock lock bot locked as resolved and limited conversation to collaborators Jan 15, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
0 participants
You can’t perform that action at this time.