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/197387754)
Release Notesv2.0.0-beta.35
v2.0.0-beta.35 (2017-02-01)
3 new flags:
--no-sort (only for run, exec and bootstrap)
By default, all tasks execute on packages in topologically sorted order as to respect the dependency relationships of the packages in question. Cycles are broken on a best-effort basis in a way not guaranteed to be consistent across Lerna invocations.
Topological sorting can cause concurrency bottlenecks if there are a small number of packages with many dependents or if some packages take a disproportionately long time to execute. The --no-sort option disables sorting, instead executing tasks in an arbitrary order with maximum concurrency.
--hoist (only for bootstrap)
Install external dependencies matching glob at the repo root so they're
available to all packages. Any binaries from these dependencies will be
linked into dependent package node_modules/.bin/ directories so they're
available for npm scripts. If the option is present but no glob is given
the default is ** (hoist everything). This option only affects the bootstrap command.
$ lerna bootstrap --hoist
Note: If packages depend on different versions of an external dependency,
the most commonly used version will be hoisted, and a warning will be emitted.
This option may also be set in lerna.json with "hoist": true or "hoist": <glob>.
--nohoist (only for bootstrap)
Do not install external dependencies matching glob at the repo root. This
can be used to opt out of hoisting for certain dependencies.
$ lerna bootstrap --hoist --nohoist=babel-*
This option may also be set in lerna.json with "nohoist": <glob>.
🚀 Enhancement
#507 Automatic hoisting of common dependencies. (@gigabo)
#547 Spawn child process for rimraf (speeds up lerna clean). (@roblg)
#543 [clean] Support --include-filtered-dependencies flag. (@roblg)
#412 Make bootstrap, exec and run commands execute packages in dependency order by default. (@seansfkelley)
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).
Version 2.0.0-beta.35 of lerna just got published.
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/197387754)Release Notes
v2.0.0-beta.35v2.0.0-beta.35 (2017-02-01)
3 new flags:
--no-sort(only for run, exec and bootstrap)By default, all tasks execute on packages in topologically sorted order as to respect the dependency relationships of the packages in question. Cycles are broken on a best-effort basis in a way not guaranteed to be consistent across Lerna invocations.
Topological sorting can cause concurrency bottlenecks if there are a small number of packages with many dependents or if some packages take a disproportionately long time to execute. The
--no-sortoption disables sorting, instead executing tasks in an arbitrary order with maximum concurrency.--hoist(only for bootstrap)Install external dependencies matching
globat the repo root so they'reavailable to all packages. Any binaries from these dependencies will be
linked into dependent package
node_modules/.bin/directories so they'reavailable for npm scripts. If the option is present but no
globis giventhe default is
**(hoist everything). This option only affects thebootstrapcommand.Note: If packages depend on different versions of an external dependency,
the most commonly used version will be hoisted, and a warning will be emitted.
This option may also be set in
lerna.jsonwith"hoist": trueor"hoist": <glob>.--nohoist(only for bootstrap)Do not install external dependencies matching
globat the repo root. Thiscan be used to opt out of hoisting for certain dependencies.
$ lerna bootstrap --hoist --nohoist=babel-*This option may also be set in
lerna.jsonwith"nohoist": <glob>.lerna clean). (@roblg)--include-filtered-dependenciesflag. (@roblg)--scope --include-filtered-dependencies. (@roblg)When running
lerna bootstrap --scope foo --include-filtered-dependenciesrun prepublish task with the same flags.cross-env.. (@wtgtybhertgeghgtwtg)isarray.. (@wtgtybhertgeghgtwtg)signal-exit.. (@wtgtybhertgeghgtwtg)object-assigned-sorted.. (@wtgtybhertgeghgtwtg)object-assign.. (@wtgtybhertgeghgtwtg)inquirerdependency. (@wtgtybhertgeghgtwtg)Committers: 9
Commits
The new version differs by 48 commits .
e3fc0e92.0.0-beta.3505ceaaafix version [skip ci]b35c05fupdate changelog [skip ci] (#561)77b77faBumpcross-env. (#554)560348cUpdating README:cleanrespects --include-filtered-dependencies (#558) [skip ci]5996375redo labels [skip ci] (#560)4b6f0aaDropisarray. (#559)bcaf1aaFix broken hoisting tests (#557)6e9bf13Merge pull request #507 from gigabo/hoist0b016deSpawn child process for rimraf (#547)bc93b96Bumpsignal-exit. (#549)84b81abUse real Object.assign now that we're off of 0.10/0.123a61c69Don't prune the repo root when hoisting (#67)4eaf88eKill some duplicate methodsf7b8b3eAutomatic hoisting of common dependencies to repo root (#36)There are 48 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: