feat(inbox): remove scale-gated rollout for signals inbox#2533
Merged
Conversation
The inbox was gated behind the `inbox-gated-due-to-scale` feature flag, swapping the inbox for a "rolling out gradually" pane for large-scale orgs. Remove the gate so signals inbox is available to everyone, along with the now-dead GatedDueToScalePane, the flag constant, and the gate-only analytics (is_gated_due_to_scale property and INBOX_INTEREST_REGISTERED event) across the desktop and mobile apps. Generated-By: PostHog Code Task-Id: b79c45ea-0fdf-485e-8e13-3698a12bbf99
|
React Doctor found 2 issues in 1 file · 2 warnings. 2 warnings
Reviewed by React Doctor for commit |
Contributor
|
Reviews (1): Last reviewed commit: "feat(inbox): remove scale-gated rollout ..." | Re-trigger Greptile |
VojtechBartos
approved these changes
Jun 9, 2026
skoob13
approved these changes
Jun 9, 2026
k11kirky
approved these changes
Jun 9, 2026
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
4 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.
Problem
The signals Inbox was gated behind the
inbox-gated-due-to-scalefeature flag. Orgs flagged in were shown a "we're rolling out self-driving gradually" pane (GatedDueToScalePane) instead of their inbox, and the inbox data wasn't loaded for them. We no longer need this rollout gate — the inbox should be available to everyone.Changes
Removed the scale gate end to end:
InboxView.tsx— dropped theuseFeatureFlag(INBOX_GATED_DUE_TO_SCALE_FLAG)branch and the gate-onlyINBOX_VIEWEDtracking effect; now always renders<InboxSignalsTab />.InboxEmptyStates.tsx— deleted the now-unusedGatedDueToScalePanecomponent and its dangling imports.constants.ts— removed theINBOX_GATED_DUE_TO_SCALE_FLAGconstant.is_gated_due_to_scaleproperty fromInboxViewedPropertiesand theINBOX_INTEREST_REGISTEREDevent (desktopanalytics.ts,InboxSignalsTab.tsx, and the mobile equivalents).No backend changes are needed in
posthog/posthog— that repo never referenced this flag (the flag was configured purely in PostHog). The web Inbox there is gated by a separateproduct-autonomyflag, which is unrelated to this scale gate and left untouched.How did you test this?
pnpm typecheckinapps/code— 0 errors.biome checkon all changed files — clean.vitest run apps/mobile/src/features/inbox/utils.test.ts— 11/11 passing.Automatic notifications
Created with PostHog Code