You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-10-21] Upgrade react-navigation to 7.11.2 #101715
App is several minors behind on react-navigation. @react-navigation/native is pinned at 7.1.33.
Solution
Upgrade @react-navigation/native to 7.11.2 and bump the sibling packages to their compatible releases. Current pinned versions in package.json:
@react-navigation/native — 7.1.33 → 7.11.2
@react-navigation/core — 7.21.12
@react-navigation/bottom-tabs — 7.15.5
@react-navigation/native-stack — 7.14.5
@react-navigation/material-top-tabs — 7.4.19
@react-navigation/stack — 7.8.5
@react-navigation/devtools — 7.0.52 (dev)
The react-navigation packages version independently, so 7.11.2 applies only to @react-navigation/native. Pick the matching releases for the siblings.
Review the changelogs for breaking changes, update any affected navigation code and types, and regression-test navigation on web, iOS, Android, and hybrid.
Your update covers today's overdue check. Reply with @MelvinBot <request> if you want help with the upgrade PR, such as reviewing changelogs or testing navigation on web.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.8-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-10-21. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
⚠️ Looks like this issue was linked to a Deploy Blocker #104154
@shubham1206agra this issue and/or PR mention a deploy blocker or a regression. Before the payment date, post one of the three options in step 20 of the C+ doc: it was a regression, it was not, or you did not review the offending PR. If you don't post, the default is to reduce payment.
Activity
docs: record where the inactive-card clip fix landed upstream
BartekObudzinski commentedon Sep 24, 2026
Created a draft pr and park the work for now to wait this pr #101093 to be merged, then i will continue work on this ticket
melvin-bot commentedon Sep 24, 2026
@shubham1206agra Whoops! This issue is 2 days overdue. Let's get this updated quick!
BartekObudzinski commentedon Sep 25, 2026
@MelvinBot Work is in progress, we waits for one PR to be merged mentioned above and finish manual testing
MelvinBot commentedon Sep 25, 2026
Thanks for the update,
BartekObudzinski. Here is the current state:Your update covers today's overdue check. Reply with
@MelvinBot <request>if you want help with the upgrade PR, such as reviewing changelogs or testing navigation on web.view run
melvin-bot commentedon Sep 28, 2026
@shubham1206agra Still overdue 6 days?! Let's take care of this!
BartekObudzinski commentedon Sep 29, 2026
Still waiting for the pr to be merged
11 remaining items
melvin-bot commentedon Oct 14, 2026
@shubham1206agra
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.8-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-10-21. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
melvin-bot commentedon Oct 15, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Oct 19, 2026
@shubham1206agra Huh... This is 4 days overdue. Who can take care of this?
melvin-bot commentedon Oct 20, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Oct 20, 2026
Payment Summary
Resolving PRs:
Upgrade react-navigation to newest eligible 7.x releases #103699
Reviewer: @shubham1206agra owed $175 via NewDot
Contributor: @BartekObudzinski does not require payment (Contractor)
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Oct 21, 2026
@shubham1206agra this issue and/or PR mention a deploy blocker or a regression. Before the payment date, post one of the three options in step 20 of the C+ doc: it was a regression, it was not, or you did not review the offending PR. If you don't post, the default is to reduce payment.
shubham1206agra commentedon Oct 22, 2026
@mallenexpensify Not related to this issue. See #104154 (comment)
mallenexpensify commentedon Oct 22, 2026
Payment Summary
Contributor+: @shubham1206agra due $175 via NewDot