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

## The devDependency [lerna](https://github.com/lerna/lerna) was updated from `3.14.1` to `3.14.2`.

🚨 [View failing branch](https://github.com/linkedin/opticss/compare/master...linkedin:greenkeeper%2Flerna-3.14.2).

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](https://travis-ci.org/linkedin/opticss/builds/543509642?utm_source=github_status&utm_medium=notification)).

---

Release Notes for v3.14.2

3.14.2 (2019-06-09)

Bug Fixes

• bootstrap: Respect --force-local option (#2104) (c2fb639)


• child-process: Ensure adjacent prefixes are always a different color (5a10146)


• npm-publish: Use generated manifest when publishing subdirectory (b922766), closes #2113


• publish: Allow per-leaf subdirectory publishing (ea861d9), closes #2109


• version: Remove unused dependency (285bd7e)

Commits

The new version differs by 10 commits.

• b22345b chore(release): v3.14.2


• b922766 fix(npm-publish): Use generated manifest when publishing subdirectory


• ea861d9 fix(publish): Allow per-leaf subdirectory publishing


• c2fb639 fix(bootstrap): Respect --force-local option (#2104)


• 4f15361 docs(version): Fix typo in option header (#2120)


• 94fed60 docs: Add legacy fields to lerna.json section (#2108) [skip ci]


• 285bd7e fix(version): Remove unused dependency


• 5a10146 fix(child-process): Ensure adjacent prefixes are always a different color


• c4d165a docs: Add disclaimer that Lerna is not a deployment tool (#2089)


• 9dc2bc5 docs: Indicate that even single-use deps are hoisted (#2090)

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:

Start with the failing branch and the Travis CI build linked in the issue, then compare the project’s dependency configuration before and after the lerna 3.14.2 update. Trace the reported build failure to its cause and verify that the build and tests pass with a documented dependency change.

Written by the indexing model from the issue text.