An in-range update of eslint-config-pretty is breaking the build 🚨

[greenkeeper]

Version 2.1.0 of eslint-config-pretty just got published.

Branch	Build failing 🚨
Dependency	eslint-config-pretty
Current Version	2.0.2
Type	devDependency

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

As eslint-config-pretty 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 failed Details

---

Release Notes

v2.1.0

2.1.0 (2017-09-02)

✨ Features

• base: Add function-paren-newline rule (a105db7), closes #25

🚨 Tests

• Use nyc configuration from package.json (cd8e074)

⚙️ Continuous Integrations

• travis: Retry npm install if it fails (28da4ad)

♻️ Chores

• package: update eslint to version 4.6.0 (7131c2f)

Commits

The new version differs by 4 commits.

• a105db7 feat(base): Add function-paren-newline rule
• 7131c2f chore(package): update eslint to version 4.6.0
• 28da4ad ci(travis): Retry npm install if it fails
• cd8e074 test: Use nyc configuration from package.json

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 🌴

[greenkeeper]

After pinning to 2.0.2 your tests are passing again. Downgrade this dependency 📌.

[greenkeeper]

Version 2.1.1 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes

v2.1.1

2.1.1 (2017-09-02)

🐛 Bug Fixes

• prettier: disable function-paren-newline rule (e5d69ec)

Commits

The new version differs by 1 commits.

• e5d69ec fix(prettier): disable function-paren-newline rule

See the full diff