Why does npm still show 0.6.1 as latest?

[jednano]

Why does npm still show 0.6.1 as latest when there are clearly 1.1.1 releases? I believe this is contributory to my project, blink, showing an out-of-date dependencies Gemnasium badge.

This is because one of my dependencies gulp-util depends on through2@^0.6.1. I submitted gulpjs/gulp-util#66 as well, but it would help to see a changelog or release notes of some kind as to the changes between 0.6.1 and 1.1.1.

[rvagg]

Currently the 1.x.x stream is reserved for a stream3 implementation, based on readable-stream@1.1.x which in turn comes from Node core 0.11. I wouldn't recommend relying on it which is why it isn't @latest yet but streams3 has stabilised so there shouldn't be any great problem with it. Just understand that they work a little differently is you must use it.

[jednano]

Thanks @rvagg it looks like Gemnasium needs to be more accurate then, perhaps, with how they detect what is and is not up-to-date.