Skip to content

fix: use the updated eval field instead evalReason #198

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
Merged
kaushalkapasi merged 1 commit into from
Aug 27, 2025
Merged

fix: use the updated eval field instead evalReason #198

kaushalkapasi merged 1 commit into from
Aug 27, 2025

Conversation

@kaushalkapasi
Copy link
Contributor

@kaushalkapasi kaushalkapasi commented Aug 27, 2025

  • fix: update android and ios channels to properly populate eval reasons using the eval field instead of deprecated evalReason

@kaushalkapasi
fix: use the updated eval field instead evalReason in the android and…
ac0a6ca 
… ios channels to properly populate eval reasons
@kaushalkapasi kaushalkapasi requested a review from a team as a code owner August 27, 2025 17:50
@kaushalkapasi kaushalkapasi merged commit 5e71501 into main Aug 27, 2025
4 checks passed
@kaushalkapasi kaushalkapasi deleted the fix-missing-android-ios-missing-new-eval-field branch August 27, 2025 18:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jsalaber jsalaber jsalaber approved these changes

Assignees

No one assigned

Labels

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@kaushalkapasi @jsalaber