feat(preprod): Check for actual build data when showing mobile builds tab#112525
Merged
NicoHinderling merged 2 commits intomasterfrom Apr 8, 2026
Merged
feat(preprod): Check for actual build data when showing mobile builds tab#112525NicoHinderling merged 2 commits intomasterfrom
NicoHinderling merged 2 commits intomasterfrom
Conversation
… tab Query the builds endpoint with per_page=1 to check if preprod builds exist for the selected projects and time range. Show the Mobile Builds tab if either actual builds data exists or the project has a mobile platform (existing fallback). The probe query is gated behind the preprod-frontend-routes feature flag and uses a 60s stale time to avoid unnecessary refetches. Refs EME-706 Co-Authored-By: Claude <noreply@anthropic.com>
github-actions
bot
added
the
Scope: Frontend
mtopo27
approved these changes
Apr 8, 2026
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
![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.
Reviewed by Cursor Bugbot for commit 851925b. Configure here.
…etch Add MockApiClient response for /builds/ endpoint in release list tests. Use keepPreviousData to prevent the mobile builds tab from flickering when query keys change during filter updates.
george-sentry
pushed a commit
that referenced
this pull request
Apr 9, 2026
… tab (#112525) Adjust the Mobile Builds tab visibility on the Releases page to also check for actual build data, not just whether the project has a mobile platform. Previously, the tab showed purely based on `isMobileRelease()` — a client-side platform check. Now we also probe the existing `/builds/` endpoint with `per_page=1` to see if any preprod builds exist for the selected projects and time range. The tab shows if either condition is true: 1. The builds endpoint returns at least one result 2. At least one selected project has a mobile platform (existing fallback) The probe query is gated behind the `preprod-frontend-routes` feature flag and uses a 60s stale time. Only date-related params are passed to avoid spurious refetches from unrelated URL query changes. Refs EME-706 --------- Co-authored-by: Claude <noreply@anthropic.com>
3 tasks
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.
Adjust the Mobile Builds tab visibility on the Releases page to also check
for actual build data, not just whether the project has a mobile platform.
Previously, the tab showed purely based on
isMobileRelease()— a client-sideplatform check. Now we also probe the existing
/builds/endpoint withper_page=1to see if any preprod builds exist for the selected projectsand time range. The tab shows if either condition is true:
The probe query is gated behind the
preprod-frontend-routesfeature flagand uses a 60s stale time. Only date-related params are passed to avoid
spurious refetches from unrelated URL query changes.
Refs EME-706