haraka / haraka-utils

Haraka's general purpose utilities
https://www.npmjs.com/package/haraka-utils
MIT License
2 stars 4 forks source link

An in-range update of eslint-plugin-haraka is breaking the build 🚨 #8

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 1.0.9 of eslint-plugin-haraka just got published.

Branch Build failing 🚨
Dependency eslint-plugin-haraka
Current Version 1.0.8
Type devDependency

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

As eslint-plugin-haraka 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 :muscle:

Status Details - ❌ **continuous-integration/appveyor/branch** Waiting for AppVeyor build to complete [Details](https://ci.appveyor.com/project/msimerson/haraka-utils/build/1.0.4) - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/haraka/haraka-utils/builds/276297343?utm_source=github_status&utm_medium=notification)

Commits

The new version differs by 1 commits.

  • 87ab6c2 remove no-useless-escape rule (inherited from recommended)

See the full diff

Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 7 years ago

After pinning to 1.0.8 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.