Bower list doesn't match my dependencies versions

[guillaumevincent]

Bower list command show updates available but doesn't respect dependencies versions

example bower.json :

{
    "dependencies": {
        "jquery": "<2"
    }
}

bower install :

bower installing jquery#1.10.0

jquery update to 1.10.1 (bower info jquery):

jquery

  Versions:
    - 2.0.2
    - 2.0.1
    - 2.0.0
    - 1.10.1
    - 1.10.0

bower list:

bower discover Please wait while newer package versions are being discovered
...
└── jquery#1.10.0 (2.0.2 now available)

[davidmaxwaterman]

With bower#0.9.3-rc0, I get :

$ bower install
bower cloning git://github.com/components/jquery.git
bower cached git://github.com/components/jquery.git
bower fetching jquery
bower checking out jquery#1.10.1
bower copying /home/davidmaxwaterman/.bower/cache/jquery/29cb4373d29144ca260ac7c3997f4381
bower installing jquery#1.10.1

I get the same for bower#0.9.2 too.

What version of bower are you using (bower -v)?

[guillaumevincent]

bower -v
0.9.2

In my case bower list should display
bower discover Please wait while newer package versions are being discovered
...
└── jquery#1.10.0 (1.10.1 now available)

because of my dependencies requirement
"jquery": "<2"

not
└── jquery#1.10.0 (2.0.2 now available)

my question on stackoverflow : http://stackoverflow.com/questions/17085614/bower-list-matching-my-dependencies-versions/17212193

[davidmaxwaterman]

OK, so the issue is about that is in the round-brackets, I see - sorry it took me so long to understand.

In other words, you want :

(1.10.1 now available)

but you get :

(2.0.2 now available)

I think it's a reasonable request - perhaps there is some argument for always listing the latest, but both might be ok. I'll see what I can do...

[guillaumevincent]

exactly, both information would be perfect
(1.10.1 and 2.0.2 now available)

[davidmaxwaterman]

In the hope that no one duplicates my effort, I will be working on this issue.

[davidmaxwaterman]

Feel free to review PR#565 : #565

[guillaumevincent]

davidmaxwaterman:issue_562 sounds good :)
waiting for the merge, thank you

[satazor]

The rewrite got merged into master. Since this issue does not happen in the new codebase I will close this out.