[Bower] versioneye cannot resolve the correct newest versions
versioneye cannot the correct newest versions for dependecies like this <package>#<version>.
Example : https://github.com/ARCANESOFT/foundation-assets/blob/master/bower.json#L34-L37
Comments (6)
-
-
Hello @reiz
Do you have an update on this issue? For me this is a blocker because VersionEye marks all of my dependencies as outdated, which is wrong. It seems like VersionEye can't handle the
<package>#<version>
syntax correctly. It should check for the#
and take only the right side.Thank you very much for your great work so far!
-
Currently working on it.
-
- changed status to resolved
@McPringle Was fixed in this commit: https://github.com/versioneye/versioneye-core/commit/f0213f0f55fc01eee6235ddd4845a4e8e1174c86. Please review and test with your own bower.json. I added a test case but I guess it needs a couple more tweaks.
-
Hi @reiz
Looks great, seems to work well!
Thank you very much Marcus
-
Awesome :-)
- Log in to comment
Same here at my SportChef project:![Bildschirmfoto 2016-01-31 um 12.48.43.png](https://bitbucket.org/repo/oepdAR/images/1465586067-Bildschirmfoto%202016-01-31%20um%2012.48.43.png)