Resolved issue is incorrectly reopened by old release

[RubenWeijers-TomTom]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. We have an Android crash that was discovered in version 10.18.x.
2. We have shipped a fix in 10.24.0 and marked the issue as resolved in that version in Sentry.
3. Then we made a hotfix on 10.18 -> 10.18.7. This didn't include the fix for the crash.

Because 10.18.7 is created later than 10.24.0, Sentry keeps reopening the crash.

Expected Result

I would expect Sentry to check which version is newer, or which build number is higher, in order to determine if a crash should be reopened or not

Actual Result

Sentry keeps reopening the issue. It forces us to either keep it open, or archive it permanently. Neither are great

Product Area

Issues

Link

https://tomtom-navapp.sentry.io/issues/6825695691/

DSN

No response

Version

No response

[linear]

ENG-5496 Resolved issue is incorrectly reopened by old release

[getsantry]

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

[yuvmen]

Hi there, sorry for the trouble this is causing you - the problem is that the way it is set up, without following exact semver format like we define it (basically missing the package.name@ prefix) your releases are not being considered to be using semver and its going by timestamp.
You can correct this by starting to release using the full format and after a few releases depending on how many you have it should start using semver correctly.
You can read the full explanation and conditions here:
https://docs.sentry.io/platforms/javascript/configuration/releases/

[RubenWeijers-TomTom]

Thanks Yuvmen. We'll try your suggestion and let you know