Regression version comparison incorrectly identified issue as regressed, when version was older than resolved-in version

[jboulter11]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

See:
https://dropbox.sentry.io/issues/5597803787/activity/?project=4505546600087552

I do not know why this happened.

Expected Result

Sentry should have compared the version numbers 388.0.6 vs 388.0.8 and concluded there was no regression.

Actual Result

Sentry compared 388.0.6 and 388.0.8 and determined 388.0.6 to be equal to or greater than 388.0.8, which is incorrect.

Product Area

Issues

Link

https://dropbox.sentry.io/issues/5597803787/activity/?project=4505546600087552

DSN

No response

Version

No response

┆Issue is synchronized with this Jira Improvement by Unito

[getsantry]

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

[armenzg]

Hey @jboulter11 👋
Thanks for reporting. I will have a look.

[armenzg]

For anyone who ends up picking this up, this PR tries to reproduce this issue:
https://github.com/getsentry/sentry/pull/74526/files

[jboulter11]

This happened again but this time with versions using release date instead of semver: https://dropbox.sentry.io/issues/5918496859/activity/?project=4505546831036416

44d3cb5 is older than 28a9559 but it is being treated as newer and reopening the ticket here.