-
Notifications
You must be signed in to change notification settings - Fork 43
docs: add ADR about using caret ranges for npm deps #687
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
docs: add ADR about using caret ranges for npm deps #687
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.
@adamstankiewicz is there anyone else we should tag for review on this?
oeps/best-practices/oep-0067/decisions/frontend/0011-caret-ranges-dependencies.rst
Show resolved
Hide resolved
Perhaps @brian-smith-tcril and @arbrandes can provide an additional review? |
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.
Overall LGTM! Well reasoned and well worded!
I left a couple non-blocking comments, one is a tiny formatting nit, the others are about linking to relevant Renovate docs to help anyone who reads this and thinks, "what's Renovate?"
oeps/best-practices/oep-0067/decisions/frontend/0011-caret-ranges-dependencies.rst
Outdated
Show resolved
Hide resolved
Co-authored-by: Brian Smith <112954497+brian-smith-tcril@users.noreply.github.com> Co-authored-by: Sarina Canelake <sarina@axim.org>
@adamstankiewicz - I think this is ready to merge, unless you have further work to do on it? |
@sarina All set to merge on my end! Thanks! |
Adds an ADR under OEP-67 "Frontend Technology Selection"'s best practices to codify the (updated) recommendation to no longer pin dependencies in
package.json
, in favor of using caret ranges.