greenkeeper-lockfile-update exceeding travis max log length

matthewdavidson commented 5 years ago

Repo: https://github.com/Skyscanner/backpack Type: Monorepo greenkeeper-lockfile version: 2.7.1 Example travis build log: https://api.travis-ci.org/v3/job/435844871/log.txt

A couple of notable things happening here:

It seems as if greenkeeper-lockfile-update can't find the package-lock.json files for the nested packages which is strange because they definately exist:
```
Without either an "npm-shrinkwrap.json", "package-lock.json" or "yarn.lock" file present there is no need to run this script
```
greenkeeper-lockfile-update is operating on packages located within node_modules folders
The logs generated from the above eventually cause travis to terminate the build

matthewdavidson commented 5 years ago

Is this related?

matthewdavidson commented 5 years ago

Given the announcement for "native" lockfile support, do we even need to use greenkeeper-lockfile anymore? Skyscanner/backpack is 100% public.

greenkeeperio / greenkeeper-lockfile