-
Notifications
You must be signed in to change notification settings - Fork 1k
2.9.0 incompatible with angular 1.5.0 according to bower #1394
Comments
Good catch. I wonder why bower does not resolve Until we fix this, use a resolution.
|
Applied a patch
|
could you please update release here too? |
It is actually not a release in this repo. It effects the bower repo only, this one here is not published to bower. |
sorry, what I meant is that if you try to install without specifying version 2.9.0.1 then bower installs 2.9.0 |
Why not use |
Eh.. good point. That's explaining why 1.5 has been used. Ehm.. Angular (1.x) does not follow semver; and bower does not follow all details, too. Or why should <= 1.5 not work? |
My bad. No, they are not following semver, one dot off. But all releases in 1.5.x is most probably compatible with eachother. So you could support all of those. And even if <= 1.5 would work, as you wrote above, the intent is much more clear with < 1.6. At least for me. |
@knall: i think the same as tregusti that only 1.6 could allow the whole 1.5.x to be supported. given the current "<=1.5.0" at every 1.5.1, 1.5.2 etc that will fore sure follow easily you will have always to make a change and release. i would suggest to have < 1.6 to be sure to not require to release a package every time and it will all the user that using it, eventually will notice that a stupid change angular 1.5.6 will cause a breaking change for us and we will put then <=1.5.6 but at that time for a reason. |
Yes, <1.6 is fine. Hold on. |
As shown by
bower list
angular-translate is shown as incompatible with angular 1.5.0#2.9.0
─ angular#1.5.0 incompatible with >=1.2.26 <=1.5 (1.4.9 available, latest is 1.5.1-build.4601+sha.c966876)
The text was updated successfully, but these errors were encountered: