-
Notifications
You must be signed in to change notification settings - Fork 145
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
chore: pin dependencies with lockfile #729
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why would you change to Renovatebot?
Dependabot would create PRs for updating as well once we have the lock file
Co-authored-by: Michaël De Boey <[email protected]> Signed-off-by: Mario Beltrán <[email protected]>
@MichaelDeBoey Because Renovatebot is way smarter than Dependabot, has more granular control, and provides lockfile maintenance. |
@Belco90 Dependabot will update lock files as well |
@MichaelDeBoey Didn't mean just updating a dependency in the lockfile, but updating the lockfile regularly so transitive dependencies are deduped and up to date. |
@Belco90 Dependabot does that as well |
That's great! I'll check if Dependabot can do what we need then. |
🎉 This PR is included in version 5.10.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 6.0.0-alpha.15 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Checks
Changes
package-lock.json
Context
I'm tired of getting unexpected errors in CI because our dev dependencies aren't fixed by a lock file. I'm fixing them with the npm lock file.
In a follow-up PR, I'll set up Renovatebot to keep our dev dependencies up to date automatically for us (disabling dependabot too).