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

eslint-find-rules@1.9.1 breaks build 🚨 #9

Closed

Conversation

greenkeeperio-bot
Copy link

Hello 👋

🚨🚨🚨

eslint-find-rules just published its new version 1.9.1, which is covered by your current version range. After updating it in your project the build went from success to failure.

This means your software is now malfunctioning, because of this update. Use this branch to work on adaptions and fixes.

Happy fixing and merging 🌴


GitHub Release

1.9.1 (2016-05-06)

Bug Fixes

  • deps: which should be part of deps instead of devDeps (#82) (b88d1ec6)

The new version differs by 7 commits .

  • b88d1ec fix(deps):whichshould be part ofdepsinstead ofdevDeps(#82)
  • 93a68b6 feat(global): error out if being used as a global utility (#72)
  • d325a03 chore(package): update nyc to version 6.4.3 (#81)
  • a56799e Update proxyquire to version 1.7.7 🚀 (#80)
  • 6502c9f feat(no-option): display error if no options are provided (#73)
  • d3324e8 chore(package): update commitizen to version 2.8.1 (#65)
  • c480c32 chore(package): update npm-run-all to version 1.8.0 (#64)

See the full diff.


This pull request was created by greenkeeper.io.
It keeps your software up to date, all the time.

Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster ⚡

@ljharb
Copy link
Owner

ljharb commented May 7, 2016

Reported in sarbbottam/eslint-find-rules#83

@sarbbottam
Copy link

@ljharb thanks for reporting, fixed it in 1.9.2

@ljharb
Copy link
Owner

ljharb commented May 8, 2016

Done in 3ac73eb

@ljharb ljharb closed this May 8, 2016
@ljharb ljharb deleted the greenkeeper-eslint-find-rules-1.9.1 branch May 8, 2016 00:05
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.

3 participants