-
-
Notifications
You must be signed in to change notification settings - Fork 17.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
build(deps): use carat notation for dependency versions #6317
Conversation
@dpopp07 can you fetch the latest changes from the repository? It's confusing to see that some dependencies aren't updating with this policy, but that's because they actually no longer exist. |
Ah, yes - will do. I built this off of the |
It should be master in this case |
Signed-off-by: Dustin Popp <dustinpopp@ibm.com>
67b79a0
to
2abfab1
Compare
Ah, my mistake! That makes more sense. The PR is updated 👍 |
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.
thanks @dpopp07
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.
Actually, I was planning to work on similar PR. Thanks @dpopp07 ❤️
@wesleytodd can we include it in the next v5 release? |
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.
Awesome! Yes this needs to land before we do the next release. Should be good to land now I think.
This updates semver ranges to use carat notation for a number of dependencies, towards the goals in #6316. @wesleytodd I know you said that issue isn't necessary complete - so if I jumped the gun, I can make whatever updates are needed 🙂 I also used that issue as a source of truth for which dependencies should be updated - there are still some without carat notation that I can also update if desired.