An in-range update of conventional-recommended-bump is breaking the build 🚨

[greenkeeper]

The devDependency conventional-recommended-bump was updated from 4.0.4 to 4.1.1.

🚨 View failing branch.

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

conventional-recommended-bump 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 could not complete due to an error (Details).

---

Commits

The new version differs by 56 commits.

• c0314ad Publish
• 02a7b8b forcing change in git history, due to publication error
• fb4a8d1 fix: preset load error message should handle objects
• b3416cb Publish
• ad70637 build: conventional-changelog-conventionalcommits was missing from top level package.json
• dde12fe feat: conventionalcommits preset, preMajor config option (#434)
• 4eb1f55 fix: adhere to config spec (#432)
• 18f71d2 fix: address discrepancies between cc preset and spec (#429)
• 2fef568 docs(eslint): sync with upstream docs (#404)
• fecb81c chore: regenerate package-lock.json (#430)
• fbcc92e fix(filter): replace is-subset with lodash.ismatch (#377)
• 26fe91f fix(deps): update dependency through2 to v3 (#392)
• 4c09bfc fix(deps): update dependency concat-stream to v2 (#401)
• f2fb240 feat: creating highly configurable preset, based on conventionalcommits.org (#421)
• 81e03b0 Docs: fixed link to eslint doc (#417)

There are 56 commits in total.

See the full diff

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 🌴

[greenkeeper]

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