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

An in-range update of @semantic-release/changelog is breaking the build 🚨 #227

Open
greenkeeper bot opened this issue Oct 26, 2019 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Oct 26, 2019

The devDependency @semantic-release/changelog was updated from 3.0.4 to 3.0.5.

🚨 View failing branch.

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

@semantic-release/changelog 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).

Release Notes for v3.0.5

3.0.5 (2019-10-26)

Bug Fixes

Commits

The new version differs by 7 commits.

  • efcc658 fix: require Node.js >=8.16
  • 4d75adc chore(package): update xo to version 0.25.0
  • 3493e20 ci(node): set node 8 to node 8.3 and add node 12
  • 52edb8d chore(package): update clear-module to version 4.0.0
  • 80788e6 chore: remove commitizen from our dependencies
  • de20199 chore(package): update commitizen to version 4.0.0
  • 8955437 chore(package): update ava to version 2.0.0

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
Copy link
Contributor Author

greenkeeper bot commented Oct 26, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants