-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Use caret on install save #2145
Conversation
This fix brings us inline with how npm installs work and also brings us more inline with how semver is supposed to be used. Fixes #2144
58d761d
to
d06af7a
Compare
Probably we should put it in bower 2.0? |
hmm, I was thinking if this is a "breaking" change.. but I think that it is not, it is not impacting old bower.json files, and just will change the behavior a tiny bit on new installs, which brings it inline more with what people expect. |
Thought about that too and I'm all for it, however I also agree with @sheerun. Doesn't the caret ignore 0.x version updates? I don't think it will really break old packages either but people unaware of that change might be confused, especially for dependencies. We should at least communicate this very clearly. |
In that case.. ignore everything I just said 👻 |
👍 , I will let @sheerun make the final call on this one |
I bet I'll regret it, but let's try :) |
ha @sheerun :) |
We can always blame @samccone 😇 |
🔥 🏃 -------^ me |
This fix brings us inline with how npm installs work and also brings us
more inline with how semver is supposed to be used.
Fixes #2144