New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

We Mark Suspect Commits on code that hasn't released yet. #80912

Open

JoshFerge opened this issue Nov 18, 2024 · 0 comments

Member

JoshFerge commented Nov 18, 2024

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

have a code producing sentry errors and using releases in production
Create a new release for new code that is about to go out
Notice that code included in that new release can be marked as a suspect commit, even though it hasn't been released yet.

Expected Result

Code that hasn't deployed yet shouldn't be marked as a suspect commit. we should only look at the current release and previous releases

Actual Result

https://sentry.sentry.io/issues/6073157014/?project=1&referrer=github-pr-bot

release of error: https://sentry.sentry.io/releases/backend%4078ef0714288ad5a4d0ed04672cb24e6b00df2842/commits/?project=1

release of code: https://sentry.sentry.io/releases/backend%405a70f3a14bd53c67f002e35136a97dd5e9adab14/?project=1

Product Area

Issues

Link

No response

DSN

No response

Version

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment