Newer version detection is incorrect

[leggetter]

It could be that the beta tag confused things a little bit, or it could be that it treats 1.9 as newer than 1.10, which is obviously wrong.

[leggetter]

Could you provide more details to help reproduce this issue? Specifically:

1. What are the exact version numbers being compared (current vs detected newer version)?
2. What is the expected behavior vs actual behavior?
3. Can you share the relevant code or configuration where this version detection occurs?
4. Are you able to reproduce this consistently?

The screenshot helps show the issue exists, but we need more technical details to implement a proper fix.

[leggetter]

1.10.0-beta.4 compared to v1.9.1. It's saying v1.9.1 is newer than 1.10.0-beta.4.

This is wrong because from 1.10 down to 1.9 is a downgrade. Maybe there's some logic in there that kind of goes okay. It's not the newest non-beta version.

In that case, they should just not be prompted now. If they're on a beta and there's a newer non-beta, they should be prompted. If they're on a beta and there's a newer beta, they should be prompted. If they're on GA and there's a newer beta, they shouldn't be prompted to upgrade from a GA to a beta.