-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Dependencies] Lock dependency version numbers #3178
Labels
type:maintenance
tests, chores, or project maintenance
Milestone
Comments
15 tasks
unlikelyzero
added
Target:1.8.5
type:maintenance
tests, chores, or project maintenance
labels
Feb 14, 2022
I'm still seeing the caret on several packages @unlikelyzero - was this intentional? |
@khalidadil this was an older ticket that i added to #4795 |
15 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now we are using the caret (^) version specifier in package.json for most packages. This will cause npm to use the latest minor version of a package at build time (absent
package-lock.json
). This means that packages are silently and unpredictably upgraded, leading to problems when a newer package version introduces breaking changes or bugs. Experience has taught us that both happen with unfortunate regularity.The text was updated successfully, but these errors were encountered: