Packagist version badge outdated

[denis-sokolov]

The badge for filp/whoops is outdated. It shows 1.1-rc, although the 1.1 has been outed for over two weeks now:

Is there anything that can force a refresh on a badge?

[espadrine]

I get the same version on my local machine, which means it's an algorithmic issue. I would ask you to blame that guy, but it would probably be pointless. He did what seemed the simplest thing you could do: take your package's data, find the stable-looking versions, take the highest one in the default JS string ordering, based on standard lexicographical ordering, using Unicode values.

This means that '1.1-rc' is indeed higher than '1.1', but '1.1' is lower than '1.2'.

We could use semantic versioning to check for which version is highest, but you don't use that, so it wouldn't work anyway.

If you have a better idea, I'm all ears!

[denis-sokolov]

Today I learned that dropping a patch number is not valid semver. We'll fix that.
Meanwhile, I think you totally should use semantic versioning. To begin with, it just makes sense. But it's also in Packagist/Composer docs, so that's expected to be correct.

[espadrine]

Today I learned that dropping a patch number is not valid semver. We'll fix that.

Nah, that's valid semver. What isn't is having only two numbers. 1.1.1-rc is valid semver.

[denis-sokolov]

I think you misunderstood. That's what I said. Patch number is the third number.

[espadrine]

Ah, right. Gotcha.