-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
pnpm-lock.yaml desynchronized w/ package.json #147
Comments
I removed all lockfiles associated w/ npm. I am also considering removing the one associated w/ Ruby. |
We need to start having these PRs automatically approved and merged if they pass CI. I am not yet sure how that would be accomplished, but it would certainly be much load off maintaining deps. /cc @smorimoto as has contributed to https://github.com/fastify/github-action-merge-dependabot |
Okay, so no response from @smorimoto; i am going to proceed w/ getting that implemented unless anyone has any objections. |
My only concern(s) stem from potentially missing reqs outlined btwx myself and @yuvilio via email some months ago:
AFAICT, we will need to be doing some major re-hauling… In the meantime, i will simply try to get things a bit more automated, but noting that we would need to re-evaluate this strategy in the future. |
Apparently pnpm's lockfile never got updated as the package-lock.json normally would w/ PRs made by @dependabot & @renovatebot. They have now become desynchronized w/ only the pinned deps in the package.json being accurate.
The text was updated successfully, but these errors were encountered: