Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

greenkeeper PRs fail on first commit because the lockfile is not updated #177

Open
jonathanong opened this issue Jun 29, 2018 · 1 comment
Open

greenkeeper PRs fail on first commit because the lockfile is not updated #177

jonathanong opened this issue Jun 29, 2018 · 1 comment
Labels
waiting for user

Comments

@jonathanong
Copy link

what's the solution?

screen shot 2018-06-29 at 15 38 37

screen shot 2018-06-29 at 15 38 46
@jonathanong jonathanong changed the title greenkeeper PRs fail on first instance because the lockfile is not updated greenkeeper PRs fail on first commit because the lockfile is not updated Jun 29, 2018
@Realtin
Copy link
Member

Realtin commented Jul 6, 2018

What does the error on the CI say?
Could it be that the CI runs npm ci to install, which fails if package.json and package-lock.json are out of sync. The solution for that is to define the install command to be npm install instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
waiting for user
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@janl @Realtin @jonathanong