Skip to content

Conversation

greenkeeper[bot]
Copy link

@greenkeeper greenkeeper bot commented Dec 1, 2017

Version 8.0.3 of babel-eslint was just published.

Dependency babel-eslint
Current Version 8.0.1
Type devDependency

The version 8.0.3 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of babel-eslint.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.


Commits

The new version differs by 11 commits ahead by 11, behind by 1.

  • 1f220c2 8.0.3
  • cf5ab03 Fix mocha command path.
  • 0609da8 Lock down dependency versions.
  • 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

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 🌴

@coveralls
Copy link

Coverage Status

Coverage remained the same at 94.444% when pulling 3828cfc on greenkeeper/babel-eslint-8.0.3 into 4e965b0 on master.

greenkeeper bot added a commit that referenced this pull request Dec 24, 2017
@greenkeeper
Copy link
Author

greenkeeper bot commented Dec 24, 2017

Version 8.1.0 just got published.

Update to this version instead 🚀

Release Notes v8.1.0

Use ESLint's API to customize scope analysis and avoid monkeypatching: #542

Commits

The new version differs by 3 commits.

  • 893a5e3 8.1.0
  • bba9d00 Re-add parseNoPatch function (accidentally removed) (#557)
  • dbc6546 Use new scopeManager/visitorKeys APIs (#542)

See the full diff

greenkeeper bot added a commit that referenced this pull request Dec 25, 2017
@greenkeeper
Copy link
Author

greenkeeper bot commented Dec 25, 2017

Version 8.1.1 just got published.

Update to this version instead 🚀

Commits

The new version differs by 2 commits.

  • d84b236 8.1.1
  • e4bed5a Fix: Prevent parseForESLint() behavior from changing after parse() is called (fixes #558)(#559)

See the full diff

greenkeeper bot added a commit that referenced this pull request Dec 26, 2017
@greenkeeper
Copy link
Author

greenkeeper bot commented Dec 26, 2017

Version 8.1.2 just got published.

Update to this version instead 🚀

Commits

The new version differs by 3 commits.

  • 36bf8b4 8.1.2
  • 5aaf0e1 Fix: add Literal type to visitorKeys (#562)
  • bf9092a Fix: ignore eval (fixes #560) (#561)

See the full diff

greenkeeper bot added a commit that referenced this pull request Jan 9, 2018
@greenkeeper
Copy link
Author

greenkeeper bot commented Jan 9, 2018

Version 8.2.0 just got published.

Update to this version instead 🚀

Commits

The new version differs by 4 commits.

  • ef27670 8.2.0
  • eba5920 Add other parser plugins, update yarn.lock (#569)
  • e201fb4 Make 2018 the default ecmaVersion for rules relying on parserOptions (#556)
  • 1dedd1b update babel packages (#565)

See the full diff

greenkeeper bot added a commit that referenced this pull request Jan 9, 2018
@greenkeeper
Copy link
Author

greenkeeper bot commented Jan 9, 2018

Version 8.2.1 just got published.

Update to this version instead 🚀

Commits

The new version differs by 2 commits.

See the full diff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant