Skip to content

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

Open
@greenkeeper

Description

@greenkeeper

Version 6.3.6 of semantic-release just got published.

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

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

As semantic-release is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details,- ✅ coverage/coveralls First build on greenkeeper/semantic-release-6.3.6 at 100.0% Details

Release Notes v6.3.6

<a name"6.3.6">

6.3.6 (2017-01-13)

Bug Fixes

  • package:
    • update github to version 8.0.0 (afd6ab75)
    • update nopt to version 4.0.0 (b10c8910)
Commits

The new version differs by 8 commits0.

  • af90de9 Merge pull request #355 from semantic-release/dep-updates
  • aa012b3 Merge branch 'greenkeeper/tap-9.0.0' into dep-updates
  • 5724b19 Merge branch 'greenkeeper/github-8.0.0' into dep-updates
  • 97a8e73 Merge branch 'caribou' into greenkeeper/nopt-4.0.0
  • 51e12a3 docs(package): fix 'home' link
  • afd6ab7 fix(package): update github to version 8.0.0
  • f80e056 chore(package): update tap to version 9.0.0
  • b10c891 fix(package): update nopt to version 4.0.0

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions