Skip to content
This repository has been archived by the owner on Aug 21, 2019. It is now read-only.

Update @researchgate/eslint-config-rg-node-babel to the latest version 🚀 #60

Merged

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Jun 29, 2018

Version 4.0.0 of @researchgate/eslint-config-rg-node-babel was just published.

Dependency @researchgate/eslint-config-rg-node-babel
Current Version 3.0.0
Type devDependency

The version 4.0.0 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 @researchgate/eslint-config-rg-node-babel.

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.


Release Notes v4.0.0

Bug Fixes

  • set npmClient=yarn in lerna.json (#12) (b45bfc7)

Features

  • base: Add no-cond-assign and no-new-func (ff85fa1)
  • deps: update dependency eslint to v5 (#14) (798ac50)

BREAKING CHANGES

  • deps: Requires eslint v5
  • base: Add no-cond-assign and no-new-func
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 🌴

@danez danez merged commit 9d9d0ac into master Jun 29, 2018
@greenkeeper greenkeeper bot deleted the greenkeeper/@researchgate/eslint-config-rg-node-babel-4.0.0 branch June 29, 2018 11:50
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants