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 lerna is breaking the build 🚨 #351

Closed
greenkeeper bot opened this issue Apr 25, 2019 · 1 comment · Fixed by #358
Closed

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

greenkeeper bot opened this issue Apr 25, 2019 · 1 comment · Fixed by #358

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Apr 25, 2019

The devDependency lerna was updated from 3.13.3 to 3.13.4.

🚨 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
  • ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for v3.13.4

3.13.4 (2019-04-24)

Bug Fixes

  • import: Avoid "unrecognized input" error from colors when using --flatten (#2037) (51625fa), closes #1644
  • version: Resolve prerelease for version without bump (#2041) (aa11325)
  • version: Search for complete tag prefix when composing GitHub releases (024a6ab), closes #2038
Commits

The new version differs by 8 commits.

  • e32da08 chore(release): v3.13.4
  • 024a6ab fix(version): Search for complete tag prefix when composing GitHub releases
  • 090e180 test(version): Ensure prompt default preserves prereleaseId
  • c1aafe7 test(version): Simplify version-bump assertions
  • cdc5e46 chore: bump dev deps, reset lockfile
  • aa11325 fix(version): Resolve prerelease for version without bump (#2041)
  • 8ccf844 test(exec/run): Explicitly test --no-sort
  • 51625fa fix(import): Avoid "unrecognized input" error from colors when using --flatten (#2037)

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 Apr 25, 2019

After pinning to 3.13.3 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

Successfully merging a pull request may close this issue.

0 participants