fix: correctly handle multiple variants for same statistic on same day [MIM-2523]#3629
Open
fix: correctly handle multiple variants for same statistic on same day [MIM-2523]#3629
Conversation
github-actions
bot
changed the title
|
Glenruben
approved these changes
Feb 17, 2026
Contributor
Glenruben
left a comment
Glenruben
left a comment
There was a problem hiding this comment.
This seems to have fixed the issue, have ran locally 👍
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Pull Request
Description
The calendar previously deduplicated releases by statistic id only,
which caused variants published on the same day to be treated as duplicates.
The deduplication key now includes both statistic id and variant id,
ensuring all variants are displayed.
Additionally, the id/key handling has been strengthened to avoid
weak or ambiguous keys in future scenarios.
Link to ticket: MIM-2523