Changelog updates for Destinations, Passkeys, React Native SDK, and Mixpanel Agent#121
Changelog updates for Destinations, Passkeys, React Native SDK, and Mixpanel Agent#121mintlify[bot] wants to merge 1 commit into
Conversation
- Updated changelogs.mdx Mintlify-Source: dashboard-editor
Confidence Score: 4/5Safe to merge once the Bonferroni/BH temporal ordering is clarified. The only substantive concern is the April Bonferroni entry describing BH auto-switching as already live, while BH has its own changelog entry two months later. If the two corrections actually shipped together in April, no change is needed; if not, the cross-reference should be removed to avoid misleading readers. changelogs.mdx — specifically the Bonferroni Correction entry at the 2026-04-05 section.
|
| Filename | Overview |
|---|---|
| changelogs.mdx | Adds 8 new changelog entries (React Native SDK, Breakdowns, BH Correction, CUPED, Winsorization, Pre-Experiment Bias, SRM, Bonferroni); one entry (Bonferroni, Apr 2026) cross-references Benjamini-Hochberg as already live despite BH having a separate June 2026 entry. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["changelogs.mdx"] --> B["2026-07-10\nReact Native SDK (Feature Flags GA)"]
A --> C["2026-06-18\nBreakdowns in Experiment Results"]
A --> D["2026-06-18\nBenjamini-Hochberg Correction"]
A --> E["2026-04-05\nCUPED"]
A --> F["2026-04-05\nWinsorization"]
A --> G["2026-04-05\nPre-Experiment Bias Health Check"]
A --> H["2026-04-05\nSample Ratio Mismatch (SRM)"]
A --> I["2026-04-05\nBonferroni Correction"]
I -. "references BH (June feature?)" .-> D
Reviews (1): Last reviewed commit: "Updated mintlify pages" | Re-trigger Greptile
|
|
||
| - **Control family-wise error:** Bonferroni divides your confidence threshold by the number of comparisons (metrics × non-control variants), reducing false positives across the whole experiment. | ||
| - **Trust multi-metric readouts:** When you track many metrics at once, Bonferroni makes sure a single flashy result isn't just noise. | ||
| - **Pair with the right method:** For segmented results, Mixpanel automatically switches to Benjamini-Hochberg, which preserves more power at scale. |
There was a problem hiding this comment.
Forward-reference to an unreleased feature
The Bonferroni Correction entry is dated 2026-04-05, but it mentions that Mixpanel "automatically switches to Benjamini-Hochberg" for segmented results — a capability whose dedicated changelog entry is dated two months later (2026-06-18). A reader finding the April entry would encounter a claim about behaviour that the product doesn't surface until June. Can you confirm both corrections shipped together in April, or should the BH cross-reference be dropped from the April entry?
More backlog catchup.
React Native SDK
BHC
Breakdowns in Experiments
CUPED
Winsorization
Pre-experiment Bias
SRM
Bonferroni Correction
Mintlify
0 threads from 0 users in Mintlify