Skip to content

Deploy Checklist: New Expensify 2026-09-21 #101773

Closed

Description

@OSBotify

Release Version: 9.4.91-3
Compare Changes: production...staging
Mobile-Expensify Changes: https://github.com/Expensify/Mobile-Expensify/compare/production...staging

This release contains changes from the following pull requests:

Mobile-Expensify PRs:

Internal QA:

Deploy Blockers:

Chronologically ordered merged PRs (oldest first)
  1. [No QA] [Docs] Fix card connection issues: reauthenticate vs. broken connection troubleshooting #99299
  2. 97187: Android - Show history button is not displayed in Concierge chat #99605
  3. fix: infinite loading in onboarding join workspace step #86076
  4. Mobile-Expensify submodule update to 9.4.90-1 — Adhoc Build
  5. Use standard medium button styling for report system message payment CTAs #101505
  6. Fix Copilot account search regressions #100371
  7. [Payment due @suneox] Add validate code page for CloseAccount #99416
  8. [Internal QA] Add Vendor column to expense Search and report tables #101410
  9. Bundle native builds with Re.Pack + OXC transform pipeline #99407
  10. Stop the settlement frequency page blocking itself after saving Daily #101661
  11. Fix invoice fields collision, downgrade, and copy root causes #101470
  12. Attribute thread summary avatars to the copilot who commented #100012
  13. [No QA] Enable prebuild react-native artifacts for iOS standalone NewDot app #100957
  14. Show up to three report fields per row and edit them inline #100735
  15. [Payment due @bernhardoj] Update NewDot onboarding employee ranges #97021
  16. [Payment due @huult] Add import settings for IES custom dimensions #101315
  17. Resolve deprecated reimbursement choices so Pay stays available #101713
  18. [Payment due @linhvovan29546] fix: send domainAccountID when setting card feed transaction liability #101046
  19. Fix Self-DM distance tab visibility for personal destinations #100829
  20. Scope the distance commuter-exclusion check to the expense destination #101022
  21. Feat: show skeleton loaders on initial home load #99560
  22. Fix android tooltip overflow #101652
  23. Match Task title row arrow style and placement to the other push rows #100245
  24. perf: preload the Reports tab so the first Inbox open runs the warm path #100042
  25. Mobile-Expensify submodule update to 9.4.90-2 — Adhoc Build
  26. Gate "Submit to my employer" on the workspace billing restriction #100584
  27. Fix: Side Panel composer steals focus back after opening a new chat #101217
  28. [Payment due @gijoe0295] Update Add to Apple Wallet (IOS only) #100404
  29. Mobile-Expensify submodule update to fdcaa24 — Adhoc Build
    ↳ https://github.com/Expensify/Mobile-Expensify/pull/14137
  30. Fix: keep the To-do row when only an older sibling expense report is fully held #100784
  31. Fix: don't render a copilot badge on Concierge-authored actions #101714
  32. fix: support iOS 27 - add SceneDelegate.swift #101742
  33. fix: show clear button on all SelectionList search fields #101086
  34. Wrap the Concierge feedback thumbs at large font sizes #101696
  35. Guard recently-used Onyx lists against non-array values #101025
  36. [No QA] Fix import/no-cycle - part 12 #101419
  37. refactor: extract useMoneyRequestReportColumns and useMoneyRequestReportLayout #101200
  38. Remove getPersonalDetailByEmail from getMemberAccountIDsForWorkspace #1 #101555
  39. [No QA] Add Currency and Flip buttons for NumericField and NumericInput #101116
  40. Rename Search "Date" filter to "Created date" and column to "Created" for expense reports #99216
  41. perf: skip the P2P chat scan for self-DM #101232
  42. Add search this user/agent to ProfilePage #99295
  43. Show receipt page count badge for split expenses #100361
  44. Fix cancel payment showing after the NACHA cutoff has passed #97556
  45. Apply the selected copilot role when retrying an add for an existing delegate #101660
  46. Mobile-Expensify submodule update to 9.4.91-0 — Adhoc Build
  47. Mobile-Expensify submodule update to 9.4.91-1 — 729e9bb
  48. 🍒 Cherry pick PR #101854 to staging 🍒 #101856
  49. [CP Staging] fix regression related to #98076 #101847
  50. Mobile-Expensify submodule update to 9.4.91-2 — 60f6328
  51. [CP Staging] Prefill personal detail for user created via public room #101889
  52. Mobile-Expensify submodule update to 9.4.91-3 — 1a1b184

Deployer verifications:

  • I checked Sentry for this release version and verified that this release does not introduce any new crashes. More detailed instructions on this verification can be found here.
  • I checked Sentry for the previous release version and verified that the release did not introduce any new crashes. Because mobile deploys use a phased rollout, completing this checklist will deploy the previous release version to 100% of users. More detailed instructions on this verification can be found here.
  • I checked GitHub Status and verified there is no reported incident with Actions.
    cc @Expensify/applauseleads

Activity

  1. melvin-bot commented on Sep 21, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  2. melvin-bot commented on Sep 21, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  3. melvin-bot commented on Sep 21, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  4. melvin-bot commented on Sep 21, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  5. melvin-bot commented on Sep 21, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  6. melvin-bot commented on Sep 21, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  7. melvin-bot commented on Sep 21, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  8. melvin-bot commented on Sep 22, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  9. melvin-bot commented on Sep 22, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  10. melvin-bot commented on Sep 22, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  11. melvin-bot commented on Sep 22, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  12. melvin-bot commented on Sep 22, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  13. melvin-bot commented on Sep 22, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  14. melvin-bot commented on Sep 22, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  15. melvin-bot commented on Sep 22, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  16. melvin-bot commented on Sep 22, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  17. IuliiaHerets commented on Sep 22, 2026

    @IuliiaHerets

    Regression progress is at 95%

    PRs Failing:
    #99560 failed on Web with #101855
    #99605 failed with an original issue, comment
    #100584 faced on iOS with #101835

    PRs Untested:
    Several still pending validation: Web 2 | Android 8 | iOS 10

    #100735 no QA steps, asked

  18. self-assigned this
    on Sep 22, 2026
  19. melvin-bot commented on Sep 22, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  20. IuliiaHerets commented on Sep 22, 2026

    @IuliiaHerets

    Regression was completed

    PRs Failing:
    #99295 failed with #101888
    #99560 failed on Web with #101855
    #99605 failed with an original issue, comment
    #100584 faced on iOS with #101835

    PRs Untested:
    #100404 asked
    #100735 no QA steps, asked
    #101046 asked

    Critical TCs that are failing:
    Travel with #101844
    Integrations / Gusto with #101727
    Account Settings / Settings with #93458

  21. lakchote commented on Sep 23, 2026

    @lakchote
    Contributor

    :shipit:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions