Issue
I want to know why an issue I resolved with a release option (current, next, or a specific release) did not mark as Regressed when new events came in.
Applies To
All SaaS Customers and Self-Hosted Users
Issues
Releases
Resolution
When you resolve an issue in a specific release, Sentry treats that release and earlier ones as expected. The issue only becomes Regressed when a new event comes from a newer release.
Sentry decides what’s “newer” based on the release format:
Semver (
package@version): higher version number.Non-semver (such as a commit SHA): later release creation date.
If an issue isn’t regressing as expected, check:
The new event has a release, and it’s newer than the resolved release.
For Resolved in the next release, a newer release has been created/finalized. Archived releases are skipped.
You’re using the right resolve option: regular Resolve can regress on any later event, while release-based resolves require a newer release.
Events without a release won’t regress a release-resolved issue. See Naming Releases and 3 Different Ways to Resolve Issues.