You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the All Events page (e.g., https://aaa.sentry.io/issues/xxx/events/), sorting by the "Release" column uses lexicographic sorting instead of semantic version sorting. This results in incorrect orderings where versions like 131.70.2943.13 appear higher than 131.205.2995.1.
This behavior differs from the "Resolve Issue" functionality, which correctly understands semantic versioning.
Steps to Reproduce:
Navigate to the All Events page for any issue in your instance.
Sort events by the "Release" column.
Observe that versions are sorted lexicographically (e.g., 131.70.2943.13 appears before 131.205.2995.1).
Expected Result
Releases should be sorted using semantic versioning so that higher versions (e.g., 131.205.2995.1) appear above lower versions (e.g., 131.70.2943.13).
Actual Result
Releases are sorted lexicographically:
131.70.2943.13
131.205.2995.1
131.205.2995.0
...
Product Area
Issues
Link
No response
DSN
No response
Version
No response
The text was updated successfully, but these errors were encountered:
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
On the All Events page (e.g., https://aaa.sentry.io/issues/xxx/events/), sorting by the "Release" column uses lexicographic sorting instead of semantic version sorting. This results in incorrect orderings where versions like 131.70.2943.13 appear higher than 131.205.2995.1.
This behavior differs from the "Resolve Issue" functionality, which correctly understands semantic versioning.
Steps to Reproduce:
Expected Result
Releases should be sorted using semantic versioning so that higher versions (e.g., 131.205.2995.1) appear above lower versions (e.g., 131.70.2943.13).
Actual Result
Releases are sorted lexicographically:
131.70.2943.13
131.205.2995.1
131.205.2995.0
...
Product Area
Issues
Link
No response
DSN
No response
Version
No response
The text was updated successfully, but these errors were encountered: