Jan Lehnardt
Jan Lehnardt
That’s a really weird one, it looks like package.json and `node_modules/` don’t agree with each other.
Quick heads-up for those who only have public dependencies, you can now stop using `greenkeeper-lockfile`: https://blog.greenkeeper.io/announcing-native-lockfile-support-85381a37a0d0 We’ve put all our energy behind that, and now we have time to look...
https://github.com/greenkeeperio/greenkeeper-lockfile/releases/tag/v2.7.1 should stop failing the build, and print the path that seems to go away for no reason :)
@prymitive nope.
Heya @mightyiam would you be up for rebasing this? Thanks!
Heya David, Thanks for the suggestion. Greenkeeper is already a GitHub Application, and uses short lived tokens for its main work. For lockfiles however, our users need to be able...
Is there a way to get the things that yarn is doing internally? The log isn‘t very helpful :)
Node 4 isn’t compatible with npm 6. I’d be okay with dropping Node 4 support, if nobody needs it
https://github.com/greenkeeperio/greenkeeper-lockfile/pull/183 should address the `GH_TOKEN` issue. @dominics @Toolo could you give this a try? Everything is on `master` now, but not yet on npm. Thanks!
Heya, @cormacrelf @travi @mAAdhaTTah fix should have been in here: https://github.com/greenkeeperio/greenkeeper-lockfile/pull/187 Sorry about the fuss.