Dependency badge

[Krzysztof Tomasz Zembrowski]

Dear VersionEye-Team,

Do the dependencies badges have to include a version number in the image source url?

With a version number it is necessary to update the image source url every time a version changes.

I noticed, that an image badge gets generated without stating the version number (e.g. https://www.versioneye.com/php/crewlabs:unsplash/badge.svg?style=flat), but the downside is, that it is getting cached, and it takes a couple of days till a new badge for the newest version is being generated.

Shields.io seems to have a much better approach (e.g. https://img.shields.io/versioneye/d/php/crewlabs:unsplash.svg)

The other thing: what happened to the special badges mentioned in the blog post? The current badge looks a lot a like Gemnasium's one.

Best regards, Krzysztof

[Robert Reiz]

Good Morning @zembrowski. You can use the badges without a version number. In that case it always takes the newest version for the badge status. But you are right, the badges are cached in that cased for several days. I Didn't though on this use case then implementing the cache. We could reset the badge status as soon the crawlers find a new version of the library. Will work on that today!

That's a really old blog post :-) Currently we use the badges from Shields.io, to be conform with other badges. The old badges on the blog post don't scale well, they look really bad on retina displays ;-)

[Robert Reiz]

I close this ticket because the cache time was set down to 6 hours.