You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
greenkeeper checks package new version by changing only package.json and keeps package-lock.json out-of-sync with package.json. In this case npm ci fails due to
cipm can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
and produces "breaking the build" pull requests which is not relevant.
According to this blogpost Greenkeeper has built-in support for updating lockfiles.
And I do see that GK does update the lockfile most of the time, but for some reasons, some tests with updated dependencies are not getting their lockfiles updates.
My repo's CI uses
npm ci
to install dependencies.greenkeeper checks package new version by changing only
package.json
and keepspackage-lock.json
out-of-sync withpackage.json
. In this casenpm ci
fails due toand produces "breaking the build" pull requests which is not relevant.
Example:
The text was updated successfully, but these errors were encountered: