pvdlg/conventional-changelog-metahub

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

greenkeeper opened this issue Β· 1 comments

Version 15.7.0 of semantic-release was just published.

Branch Build failing 🚨
Dependency semantic-release
Current Version 15.6.6
Type devDependency

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

semantic-release 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 v15.7.0

15.7.0 (2018-07-10)

Bug Fixes

  • do not set path to plugin config defined as a Function or an Array (f93eeb7)

Features

  • allow to define multiple generateNotes plugins (5989989)
Commits

The new version differs by 12 commits.

  • 24ce560 refactor: build plugin pipeline parameters at initialization
  • eb26254 refactor: use Object.entries rather than Object.keys
  • 50061bb refactor: remove unnecessary object destructuring
  • 5989989 feat: allow to define multiple generateNotes plugins
  • 576eb60 refactor: simplify plugin validation
  • f7f4aab refactor: use the lastInput arg to compute the prepare pipeline next input
  • 12de628 refactor: fix incorrect comments in lib/plugins/pipeline.js
  • d303286 docs: fix default value for analyzeCommits plugin
  • ed9c456 refactor: always return an Array of results/errors from a plugin pipeline
  • cac4882 docs: clarify verifyRelease plugin description
  • 09348f1 style: disable max-params warning for lib/plugins/normalize.js
  • f93eeb7 fix: do not set path to plugin config defined as a Function or an Array

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 🌴

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