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

Version 2.0.0-beta.38 of lerna just got published.

Branch	Build failing 🚨
Dependency	lerna
Current Version	2.0.0-beta.37
Type	devDependency

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

As lerna 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 :muscle:

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/danielbayerlein/honeycomb/builds/206421189)

Release Notes

v2.0.0-beta.38

v2.0.0-beta.38 (2017-02-28)

📦 🐈 Initial Yarn support and more!

🚀 Enhancement

#605 Add support for pluggable npm clients. (@gigabo)

We'll make yarn the default once we feel that it's more stable.

$ lerna bootstrap --npm-client=yarn

{
  "npmClient": "yarn"
}

This will run yarn in each package can create temp yarn.lock files while developing so you'll want to .gitignore/.npmignore these files. Ex: .gitignore: packages/*/yarn.lock

#595 Publish npm packages in topological order (@loganfsmyth)

Very important fix for Babel that we used in the last release. This prevents a timing issue when publishing where a module will try to download a package that isn't published yet because it is published before it's own dependency is published itself. We used to get many issues from users on non-public npm about "babel-types" not being found.

#608 Add a --stream option to the run command. (@gigabo)

Useful to get output for child processes immediately if using lerna run with a watch command

$ lerna run watch --stream

#624 Add versions to lerna ls. Closes #603 (@ben-eb)
#620 Feature: skip-temp-tag. (@noherczeg)

This will not create a temporary dist-tag called lerna-temp when publishing. Useful if your third party proxy doesn't support dist-tags.

$ lerna publish --skip-temp-tag

#587 Always run test and env scripts. (@simon360)

Defaults to running npm run test and npm run env

#598 Durable includeFilteredDependencies config via lerna.json. (@gigabo)

{
  "commands": {
    "bootstrap": {
      "includeFilteredDependencies": true
    }
  }
}

#596 Support sort option in lerna.json. (@gigabo)

{
  "commands": {
    "run": {
      "sort": false
    }
  }
}

#599 Explicit registry flag feature. (@noherczeg)

$ lerna publish --registry https://my-private-registry

🐛 Bug Fix

#601 Fix --ignore flag when globs are expanded to an array. (@rtsao)
#597 Support command config in either "commands" or "command". (@gigabo)
#586 Avoid exception after successful lerna diff. (@evocateur)

🏠 Internal

#604 Fix midair collision. (@doug-wade)
#594 Remove sync-exec (@wtgtybhertgeghgtwtg)

Committers: 11

Ben Briggs (ben-eb)
Bo Borgerson (gigabo)
Daniel Stockman (evocateur)
Douglas Wade (doug-wade)
Garth Kidd (garthk)
Gytis Vinclovas (Gongreg)
Logan Smyth (loganfsmyth)
Norbert Csaba Herczeg (noherczeg)
Ryan Tsao (rtsao)
simon360
wtgtybhertgeghgtwtg

Commits

The new version differs by 18 commits .

7202ecc 2.0.0-beta.38
163e22b Add support for pluggable npm clients (#605)
62a8f2a Support --skip-temp-tag when publishing (#620)
2f3b195 Add a --stream option to the run command (#608)
3ace547 Add versions to lerna ls. Fixes #603. (#624)
b595884 On import, infer targetDir base from packages glob list (#480)
d246667 lerna publish checks for changes since most recent tag in the current branch (#475)
744d036 README grammar: it's → its (#609) [skip ci]
5a4039a Always run test and env scripts (#587)
d7c1fe9 Durable includeFilteredDependencies config via lerna.json (#598)
3021dc3 Support sort option in lerna.json (#596)
2e67ed2 Fix midair collision (#604)
6b5fb91 Explicit registry flag feature (#599)
8790656 Publish npm packages in topological order. (#595)
925c0a1 Fix --ignore flag when globs are expanded to an array (#601)

There are 18 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

danielbayerlein / honeycomb