Skip to content

fix(migrations): insights starred segment migration should account for null user_ids #93734

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.

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

Merged

Conversation

DominikB2014
Copy link
Contributor

@DominikB2014 DominikB2014 requested a review from a team as a code owner June 17, 2025 18:38
@DominikB2014 DominikB2014 requested a review from markstory June 17, 2025 18:38
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jun 17, 2025
@DominikB2014 DominikB2014 enabled auto-merge (squash) June 17, 2025 18:40
Copy link

codecov bot commented Jun 17, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #93734      +/-   ##
==========================================
- Coverage   88.02%   88.02%   -0.01%     
==========================================
  Files       10328    10328              
  Lines      596023   596027       +4     
  Branches    23154    23154              
==========================================
- Hits       524661   524658       -3     
- Misses      70869    70876       +7     
  Partials      493      493              

@DominikB2014 DominikB2014 merged commit b744983 into master Jun 17, 2025
66 checks passed
@DominikB2014 DominikB2014 deleted the DominikB2014/update-migration-to-account-for-null-user-id branch June 17, 2025 18:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants