The issue has been closed

latest-release not correctly recognized #2758

staabm posted onGitHub

in a private repo we have several releases.

release numbers like 1.9.7, 1.9.8 and since today 1.10 and 1.10.0

refined github does not correctly recognize that the latest version is 1.10.0. instead it tells me that 1.9.8 is the latest version:

This is due to the cache. It's set to expire after 1 day so it's bound to show some out of date information for up to 24 hours

posted by fregante about 5 years ago

I see. Will check again tomorrow.

Maybe the cache should/could be pruned when the browser is used the create a new release?

posted by staabm about 5 years ago

Also, FYI, 1.10.0 and 1.10 are semantically the same version.

posted by sindresorhus about 5 years ago

Fund this Issue

$0.00

Funded

Pull requests