search

blackxored / commitlint-config-conventional-system

Commitlint config for conventional system extensions for scopes and more
MIT License
2 stars 0 forks source link

An in-range update of eslint-plugin-jest is breaking the build 🚨 #18

Open greenkeeper[bot] opened 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency eslint-plugin-jest was updated from 21.22.0 to 21.22.1.

🚨 View failing branch.

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

eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/blackxored/commitlint-config-conventional-system/builds/431383144?utm_source=github_status&utm_medium=notification)).
Release Notes for v21.22.1

21.22.1 (2018-09-21)

Bug Fixes

  • no-disabled-tests: fix false positives for pending() usage (#155) (fdce162), closes #149
Commits

The new version differs by 3 commits.

  • fdce162 fix(no-disabled-tests): fix false positives for pending() usage (#155)
  • 1361d59 chore: simplify semantic-release a bit (#153)
  • f4850a3 chore(docs): fixed typo (#142)

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 5 years ago

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