Skip to content

Deploy Checklist: New Expensify 2023-10-09 #29131

Closed

Description

@OSBotify

Release Version: 1.3.80-3
Compare Changes: production...staging

This release contains changes from the following pull requests:

Deploy Blockers:

Deployer verifications:

  • I checked the App Timing Dashboard and verified this release does not cause a noticeable performance regression.
  • I checked Firebase Crashlytics and verified that this release does not introduce any new crashes. 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. OSBotify commented on Oct 10, 2023

    @OSBotify
    ContributorAuthor

    🚀 All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/1.3.80-0 🚀

  2. kavimuru commented on Oct 10, 2023

    @kavimuru

    @jasperhuangg Regression TR is 81% progress. We are still validating couple PRs.

    #25543 failing with #29163 (blocker)
    #28628 failing with #29178
    Need help with these 2 PRs (not sure if our QA team can validate) #28377 (comment) and #28920 (comment)

  3. kavimuru commented on Oct 10, 2023

    @kavimuru

    @jasperhuangg Regression TR is just1% left.

    #25543 failing with #29163 (blocker)
    #28628 failing with #29178

    We have open blockers #29159, #29160, #29162, #29163, #29170, #29172, #29183, #29184 and #29186

  4. mvtglobally commented on Oct 10, 2023

    @mvtglobally

    @jasperhuangg

    Regression is completed.

    Open Blockers:
    #29159
    #29160
    #29162
    #29163
    #29170
    #29172
    #29183
    #29184
    #29186

    Unchecked PRs:
    #25543 failing with #29163 (blocker)
    #28628 failing with #29178

    Can you pls tag us if there are any CPs needed to re-test

  5. self-assigned this
    on Oct 10, 2023
  6. jasperhuangg commented on Oct 10, 2023

    @jasperhuangg
    Contributor

    @mvtglobally #29189 CP'd, should fix #29160, please retest, thanks!

  7. jasperhuangg commented on Oct 10, 2023

    @jasperhuangg
    Contributor

    #29162 is a known follow-up issue, so checking it off

  8. jasperhuangg commented on Oct 10, 2023

    @jasperhuangg
    Contributor

    #29160 was fixed by #29189, checking it off

  9. jasperhuangg commented on Oct 10, 2023

    @jasperhuangg
    Contributor

    Checking off #29172 not a blocker

  10. jasperhuangg commented on Oct 10, 2023

    @jasperhuangg
    Contributor

    Closed #29184

  11. jasperhuangg commented on Oct 10, 2023

    @jasperhuangg
    Contributor

    Closed #29186

  12. jasperhuangg commented on Oct 11, 2023

    @jasperhuangg
    Contributor

    Checking off #29221, doesn't need to be a blocker

  13. jasperhuangg commented on Oct 11, 2023

    @jasperhuangg
    Contributor

    #29183 is reproducible on prod, checking it off

  14. jasperhuangg commented on Oct 11, 2023

    @jasperhuangg
    Contributor

    Checking off #28628 since the failing QA is also reproducible on production

  15. jasperhuangg commented on Oct 11, 2023

    @jasperhuangg
    Contributor

    Checking off #29159 CP'd #29251 to fix it

  16. jasperhuangg commented on Oct 11, 2023

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