Change Details

We currently use the same `alertTypes` constant for both of these. This has a risk that somebody would see the "connect Farcaster" alert, choose to enable it, and then never see the "connect Farcaster DC" alert because `shouldSkipConnectFarcasterAlert` filters after you see the alert once. To add this new `alertTypes` constant we need to make sure it's present in the Redux store on `native`. This diff introduces a no-op migration on web to keep the store version consistent between platforms.

We currently use the same `alertTypes` constant for both of these. This has a risk that a non-staff user with a new build would see the "connect Farcaster" alert, choose to enable it, and then never see the "connect Farcaster DC" alert because `shouldSkipConnectFarcasterAlert` filters after you see the alert once. To add this new `alertTypes` constant we need to make sure it's present in the Redux store on `native`.

We currently use the same `alertTypes` constant for both of these. This has a risk that somebodya non-staff user with a new build would see the "connect Farcaster" alert, choose to enable it, and then never see the "connect Farcaster DC" alert because `shouldSkipConnectFarcasterAlert` filters after you see the alert once. To add this new `alertTypes` constant we need to make sure it's present in the Redux store on `native`. This diff introduces a no-op migration on web to keep the store version consistent between platforms.