It looks like sentry doesn’t understand semver or care about the “name of versions” in any way, just about time. I marked some stuff as fixed in version v1.2.0-rc.1 and as soon as the next event comes in sentry marks it as a regression in v1.1.3. On sentry the latter is listed higher than the former, so I think it considers it as newer.
The releases page on sentry says we need to associate commits with releases and docs say that can be done with a github integration at organization level - which I don’t have access to. Is that setup and just not working? Alternatively this info could also somehow be attached in CI at build time.