fix(releases): Exclude archived releases from "Resolve in Next Release"#106674
Merged
fix(releases): Exclude archived releases from "Resolve in Next Release"#106674
Conversation
When multiple builds share the same version number, "Resolve in Next Release" was selecting archived builds instead of the latest active one. Filter by ReleaseStatus.OPEN in both most_recent_release() and get_semver_releases() to ensure only non-archived releases are considered. Fixes GH-103441 Co-Authored-By: Claude <noreply@anthropic.com>
github-actions
bot
added
the
Scope: Backend
Add tests verifying that archived releases are excluded when resolving issues with "Resolve in Next Release". Tests cover both the helper functions (most_recent_release, greatest_semver_release) and the full update_groups flow. Co-Authored-By: Claude <noreply@anthropic.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
The most_recent_release and get_semver_releases functions previously only returned releases with OPEN status. Releases with null status (which is the default) were incorrectly excluded. Update both queries to include releases where status is either OPEN or null. Co-Authored-By: Claude <noreply@anthropic.com>
|
This comes at the right moment, we're facing this as well... |
ceorourke
approved these changes
Jan 23, 2026
Member
ceorourke
left a comment
ceorourke
left a comment
There was a problem hiding this comment.
some real fire fixes from you this week
JonasBa
pushed a commit
that referenced
this pull request
Jan 27, 2026
…e" (#106674) when using "resolve in next release" with multiple builds sharing the same version number, sentry was incorrectly selecting archived builds instead of the latest active one. this adds a filter for `ReleaseStatus.OPEN` to both `most_recent_release()` and `get_semver_releases()` to ensure only non-archived releases are considered. Fixes #103441 --------- Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
when using "resolve in next release" with multiple builds sharing the same version number, sentry was incorrectly selecting archived builds instead of the latest active one. this adds a filter for
ReleaseStatus.OPENto bothmost_recent_release()andget_semver_releases()to ensure only non-archived releases are considered.Fixes #103441