Skip to content

An in-range update of lerna is breaking the build 🚨 #25

@greenkeeper

Description

@greenkeeper

The devDependency lerna was updated from 3.4.0 to 3.4.1.

🚨 View failing branch.

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

lerna 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 failed (Details).

Commits

The new version differs by 10 commits.

  • 05a27a6 chore(release): publish v3.4.1
  • f7fdc77 fix(publish): Overwrite Yarn registry proxy when encountered
  • 06a9479 fix(publish): Set token on npm config, allow third-party registries to remain non-compliant
  • 987fd26 fix(bootstrap): Constrain npm-conf argument object to options.registry only
  • 597606c fix(add): Allow --registry option
  • 25af71d fix(npm-conf): Do not overwrite defaults with undefined cli keys
  • 159a0b0 fix(conventional-commits): Upgrade angular preset, ensure header is not duplicated
  • 9752f3e fix(conventional-commits): Upgrade dependencies
  • a60a0c3 docs: Add 'lerna create' command to README.md (#1680)
  • 265ec0c docs(readme): update independent mode instructions (#1701)

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 🌴

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