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

[greenkeeper]

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

• ✅ coverage/coveralls: First build on greenkeeper/@semantic-release/changelog-3.0.5 at 100.0% (Details).
• ✅ Test on node 12 and macOS-latest: null
• ❌ Test on node 12 and windows-latest: There are 10 failures, 0 warnings, and 0 notices.
• ✅ Test on node 12 and ubuntu-latest: null
• ✅ Test on node 10 and macOS-latest: null
• ❌ Test on node 10 and windows-latest: There are 11 failures, 0 warnings, and 0 notices.
• ✅ Test on node 10 and ubuntu-latest: null
• ✅ Test on node 8 and macOS-latest: null
• ❌ Test on node 8 and windows-latest: There are 10 failures, 0 warnings, and 0 notices.
• ✅ Test on node 8 and ubuntu-latest: null
• ✅ build: * checkout_code - Success

• test - Success
• release - Success

---

Release Notes for v3.0.5

3.0.5 (2019-10-26)

Bug Fixes

• require Node.js >=8.16 (efcc658)

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]

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.