Repository navigation
Deploy Checklist: New Expensify 2026-09-18 #101620
Description
Activity
- added🔐 LockCashDeploys 🔐Prevent new code from being deployed to stagingPrevent new code from being deployed to stagingDailyKSv2KSv2
on Sep 18, 2026 ⚠️ Looks like this issue was linked to a Deploy Blocker hereIf 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.
⚠️ Looks like this issue was linked to a Deploy Blocker hereIf 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.
checked off #101459 b/c on prod
Regression progress is at 94%
PRs Failing:
#99385 on Web, Android, iOS
#99790 on Native apps
#100583 on Web
#100693 on AndroidPRs Untested:
Several still pending validation: Web 18 | Android 17 | iOS 22#100953 - question
#101471 - question
#101507 - internal comment
https://github.com/Expensify/Mobile-Expensify/pull/14131 - question⚠️ Looks like this issue was linked to a Deploy Blocker hereIf 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.
⚠️ Looks like this issue was linked to a Deploy Blocker hereIf 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.
⚠️ Looks like this issue was linked to a Deploy Blocker hereIf 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.
⚠️ Looks like this issue was linked to a Deploy Blocker hereIf 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.
⚠️ Looks like this issue was linked to a Deploy Blocker hereIf 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.
⚠️ Looks like this issue was linked to a Deploy Blocker hereIf 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.
⚠️ Looks like this issue was linked to a Deploy Blocker hereIf 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.
⚠️ Looks like this issue was linked to a Deploy Blocker hereIf 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.
⚠️ Looks like this issue was linked to a Deploy Blocker hereIf 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.
⚠️ Looks like this issue was linked to a Deploy Blocker hereIf 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.
Regression is completed in BrowserStack
PRs Failing:
#97301 faced with #101729 Repro in Prod, checking it off
#99385 with #101689 & #101692
#99558 with #73022 & #101736
#101090 with #101754
#100454 with #100454 (comment) No need GH ticket #100454 (comment)
#100583 on Web with #101677 & #101690
#100693 on Native with #101684
#101304 faced with issues #101707, #101701 Pending validation on Web
#101317 with #101718 Repro in prod, checking it offPRs Untested:
#97947 pending validation on Web
#100953 pending validation on Web
#101376 (comment)
#101607 (comment)Regression is completed
PRs Failing:
#99385 with #101689 & #101692
#97947 with this #97947 (comment)
#99558 with #73022 & #101736
#101090 with #101754
#100454 with #100454 (comment) No need GH ticket #100454 (comment)
#100583 on Web with #101677 & #101690
#100693 on Native with #101684
#101304 faced with issues #101707, #101701, #101760PRs Untested:
#101376 (comment)
#101607 (comment)Critical TCs that are failing:
Critical Viral Path with #101182
Gusto with #101727⚠️ Looks like this issue was linked to a Deploy Blocker hereIf 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.

Release Version:
9.4.90-2Compare Changes: production...staging
Mobile-Expensify Changes: https://github.com/Expensify/Mobile-Expensify/compare/production...staging
This release contains changes from the following pull requests:
autoApproval.limitset by Classic Expensify #97301Mobile-Expensify PRs:
Internal QA:
Deploy Blockers:
Chronologically ordered merged PRs (oldest first)
9.4.83-0— Adhoc Build9.4.84-0— Adhoc BuildautoApproval.limitset by Classic Expensify #973019.4.84-1— Adhoc Build082a8b1— Adhoc Build↳ https://github.com/Expensify/Mobile-Expensify/pull/14126
9.4.84-2— Adhoc Build9.4.84-3— Adhoc Build7288901— Adhoc Build↳ https://github.com/Expensify/Mobile-Expensify/pull/14124
9.4.84-4— Adhoc Build9.4.85-0— Adhoc Build9.4.85-1— Adhoc Build9.4.86-0— Adhoc Build9.4.87-0— Adhoc Build9.4.88-0— Adhoc Build9.4.89-0— Adhoc Build0343ade— Adhoc Build↳ https://github.com/Expensify/Mobile-Expensify/pull/14131
9.4.90-0— Adhoc Build9.4.90-1— 44a83bd9.4.90-2— 9235b3fDeployer verifications:
cc @Expensify/applauseleads