Skip to content

Deploy Checklist: New Expensify 2026-10-05 #103094

Closed

Description

@OSBotify

Release Version: 9.5.3-4
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. Add avatar to bottom left of LHN #69
  2. HTML is rendered on the "optimistic" message #72
  3. Add ability to deploy production version of iOS/Android app #75
  4. Fix enabling approvals on workspaces with Smart Limit cards #102903
  5. Map payroll code and category rule columns in category spreadsheet import #102399
  6. Split report preview action buttons evenly #102349
  7. Remove the SEARCH_QUERY_BY_HASH Onyx.connect() by storing the search query on the snapshot #102432
  8. Standardize Expense Report and Expense header with predictable button placement and carousel counter #100331
  9. fix: Not here page appears briefly when copiloting into agent's account #100803
  10. Mobile-Expensify submodule update to 9.5.2-1 — Adhoc Build
  11. [No QA] Clear cache and reload before showing Update Required on web #102731
  12. Honor an explicit Spend column selection that matches the default set #101585
  13. [No QA] Docs updates for E/A#100801 Document the added a receipt system message #102458
  14. Fix error when resubmitting the work email after going back in onboarding #102843
  15. Route Search row previews through the shared LHN alternate text #101298
  16. [No QA] Mock fetch in useGettingStartedItems tests so GetRules stays off the network #103033
  17. Mobile-Expensify submodule update to 9.5.2-2 — Adhoc Build
  18. Save the workflow when "Expense from" is edited via the +N more fast edit #100434
  19. Repoint category tax default rules when a tax code is renamed #102896
  20. [Onyx bump] Bump react-native-onyx to 3.0.115 #101085
  21. feat: support inline editing for workspace settings tables #100567
  22. Remove AddDomainVerifyAccountPage page #102268
  23. Fix - Add bank account shows Not Found for unvalidated admins #102765
  24. [NoQA] Bump adm-zip to 0.6.1 to fix Dependabot alerts #102996
  25. [Payment due @eVoloshchak] Add Vendor filter to expense Search #101309
  26. [Payment due @mananjadhav] [No QA] Bump jwt from 2.10.2 to 2.10.3 #103019
  27. [No QA] Bump addressable to 2.9.0 #103026
  28. Mobile-Expensify submodule update to 3aa6514 — Adhoc Build
    ↳ https://github.com/Expensify/Mobile-Expensify/pull/14163
  29. [Payment due @daledah] Allow admins to delete corporate card transactions #100548
  30. [No QA] Fix import/no-cycle - part 13 #101423
  31. Run cheap report checks first in isApproveAction #102853
  32. Chore/remove dead list item props #102254
  33. ReportActionAvatars decompostion - PolicyExpenseChatAvatar #102060
  34. Mobile-Expensify submodule update to 4872a60 — Adhoc Build
    ↳ https://github.com/Expensify/Mobile-Expensify/pull/14167
  35. Mobile-Expensify submodule update to b126878 — Adhoc Build
    ↳ https://github.com/Expensify/Mobile-Expensify/pull/14165
  36. [No QA] Mock fetch in tests that render the GetRules prefetch #103051
  37. (Part 8) Remove Onyx.connect() for the key: ONYXKEYS.PERSONAL_DETAILS_LIST in src/libs/actions/Report.ts #101523
  38. Mobile-Expensify submodule update to 9.5.2-3 — Adhoc Build
  39. [No QA] Bump underscore to 1.13.8 to address GHSA-qpx9-hpmf-5gmw #103018
  40. Stop RHP close from refiring every Home search #100551
  41. [CFI] Open the Category list in a container anchored to its row #102665
  42. Onboarding: show interested features as tiles with subtext #102566
  43. Prioritize LHN action badges over unread mentions #102813
  44. Clear isOptimisticAction on the Concierge bank account unlock message after success #102367
  45. Show list report fields when disabledOptions is shorter than values #103060
  46. fix: Show GL codes row is not aligned center with toggle button #102856
  47. [Refactor] Move PolicyUtils into a folder and split tag helpers into tags.ts #102724
  48. Fetch policy categories and tags on demand in shared pickers #99125
  49. Remove QuickBooks links from Business Central export confirmations #102921
  50. Reapply Reconciliation - All Expenses export for card group selections with an ungrouped query #102431
  51. Mobile-Expensify submodule update to d7f7e72 — Adhoc Build
    ↳ https://github.com/Expensify/Mobile-Expensify/pull/14173
  52. Mobile-Expensify submodule update to 77a2ca2 — Adhoc Build
    ↳ https://github.com/Expensify/Mobile-Expensify/pull/14169
  53. [NO QA] Bump faraday from 1.10.4 to 1.10.6 #103022
  54. Mobile-Expensify submodule update to f39a898 — Adhoc Build
    ↳ https://github.com/Expensify/Mobile-Expensify/pull/14174
  55. [Payment due @nkdengineer] [No QA] Bump js-yaml to 3.15.2 and 4.3.2 #103000
  56. Keep the new-message pill visible when another user's message arrives in an expense report #102794
  57. Designate REST + OAuth 2.0 as the default for NetSuite connections #102240
  58. Mobile-Expensify submodule update to 177a1bb — Adhoc Build
    ↳ https://github.com/Expensify/Mobile-Expensify/pull/14155
  59. [No QA] [NoQA] Align ONL583 help docs with name-conflict errors #102822
  60. Mobile-Expensify submodule update to 9.5.2-4 — Adhoc Build
  61. Mobile-Expensify submodule update to 9.5.3-0 — Adhoc Build
  62. [cp staging] Spend - App crashes after returning to expense RHP from expense report #103202
  63. Mobile-Expensify submodule update to 9.5.3-1 — d740f9c
  64. [CP Staging] Revert "Add Vendor filter to expense Search" #103211
  65. Mobile-Expensify submodule update to 9.5.3-2 — bb3581f
  66. Mobile-Expensify submodule update to 9.5.3-3 — 62b95c7
  67. Fix report preview View button cut off on iOS Safari #103206
  68. [CP Staging] fix: preserve selected approver after fast-edit invite #103111
  69. Mobile-Expensify submodule update to 9.5.3-4 — e4355b8

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 Oct 6, 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 Oct 6, 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 Oct 6, 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 Oct 6, 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 Oct 6, 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 Oct 6, 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 Oct 6, 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. IuliiaHerets commented on Oct 6, 2026

    @IuliiaHerets

    Regression progress is at 94%

    PRs Failing:
    #101309 failed on iOS with #103145
    #102367 failed with #103156
    #102399 failed on Web with an original issue, comment
    #102794 failed with #103157 and an original issue, comment
    #102903 faced with #103159
    https://github.com/Expensify/Mobile-Expensify/pull/14155 faced with #100937 and #93931

    PRs Untested:
    #72 asked
    #75 asked
    #99125 asked
    #100548 pending validation on Web, Android, iOS
    #100803 pending validation on Android
    #102399 pending validation on iOS
    #102903 pending validation on iOS
    #103026 asked
    https://github.com/Expensify/Mobile-Expensify/pull/14163 pending validation on iOS

  9. trjExpensify commented on Oct 6, 2026

    @trjExpensify
    Contributor

    Demoted all these, feature is behind a beta.

    #103171
    #103140
    #103137
    #103136
    #103133
    #103131
    #103132
    #103129
    #103125
    #103124

  10. self-assigned this
    on Oct 6, 2026
  11. kavimuru commented on Oct 6, 2026

    @kavimuru

    Regression is completed.

    PRs Failing:
    #101309 failed on iOS with #103145
    #102367 failed with #103156 repro in PROD. Can we check it off?
    #102399 failed on Web with original bug #101939, #102399 (comment)
    #102794 failed with #103157 and an #102094, #102794 (comment)
    #102903 failing with #103159 repro in PROD, checking it off
    https://github.com/Expensify/Mobile-Expensify/pull/14155 faced with #100937 and #93931
    #102431 (step 6) failing with #103163 repro in PROD checking it off

    PRs Untested:
    #72 (comment)
    #75 (comment)
    #99125 (comment)

  12. melvin-bot commented on Oct 6, 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. Beamanator commented on Oct 6, 2026

    @Beamanator
    Contributor

    #103145 fixed by #103211

  14. melvin-bot commented on Oct 6, 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. puneetlath commented on Oct 6, 2026

    @puneetlath
    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