Closed elenadimitrova closed 7 years ago
Excellent observation! By my estimation, we’d accept a PR that would read a GK_LOCK_YARN_OPTS
environment variable that then get passed into yarn
here: https://github.com/greenkeeperio/greenkeeper-lockfile/blob/master/lib/update-lockfile.js#L37
Would you be interested in providing a PR?
I took a shot at it here: #78. Feel free to review :)
https://github.com/greenkeeperio/greenkeeper-lockfile/pull/78 is now merged :)
The way we update the lock file currently is using the
--ignore-engines
option as we're using packages on node 4 which require a higher version (e.g. 6.5), one example below Therefore thegreenkeeper-lockfile-update
command in CI fails with error e.g:We should be able to pass options to yarn via the
greenkeeper-lockfile-update
script