Skip to content
This repository has been archived by the owner on Oct 1, 2024. It is now read-only.

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

Closed
greenkeeper bot opened this issue Mar 23, 2017 · 0 comments
Closed

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

greenkeeper bot opened this issue Mar 23, 2017 · 0 comments
Labels
🤷 no/invalid This cannot be acted upon

Comments

@greenkeeper
Copy link

greenkeeper bot commented Mar 23, 2017

Version 7.2.1 of babel-eslint just got published.

Branch Build failing 🚨
Dependency babel-eslint
Current Version 7.2.0
Type devDependency

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 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Commits

The new version differs by 6 commits .

  • 3cda62e 7.2.1
  • 5626de1 Remove left over eslint 2 estraverse code (#452)
  • b5fb53b Fix type param and interface declaration scoping (#449)
  • f1cee0f Remove lodash dependency (#450)
  • eb05812 Format non-regression errors for legibility (#451)
  • 7972a05 Update README.md with codeFrame option (#448)

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 🌴

@wooorm wooorm added the 🤷 no/invalid This cannot be acted upon label Aug 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🤷 no/invalid This cannot be acted upon
Development

No branches or pull requests

2 participants