Skip to content

Deploy Checklist: New Expensify 2024-02-15 #36558

Closed

Description

@github-actions

Release Version: 1.4.42-5
Compare Changes: production...staging

This release contains changes from the following pull requests:

Internal QA:

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 Feb 15, 2024

    @OSBotify
    Contributor

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

  2. Julesssss commented on Feb 15, 2024

    @Julesssss
    Contributor

    I verified the InternalQA issue here. Checking off.

  3. Beamanator commented on Feb 15, 2024

    @Beamanator
    Contributor

    Reducing #36575 to NAB status

  4. Beamanator commented on Feb 15, 2024

    @Beamanator
    Contributor

    Also demoting #36576 since there's nothing broken, and this is hopefully not a high traffic page

  5. Beamanator commented on Feb 15, 2024

    @Beamanator
    Contributor

    Similarly, demoting #36577 b/c it's weird but not necessarily a blocker

  6. Julesssss commented on Feb 15, 2024

    @Julesssss
    Contributor

    Checking off blocker #36595 as it's a minor issue

  7. Beamanator commented on Feb 15, 2024

    @Beamanator
    Contributor

    Demoting #36601 since it's a Troubleshooting action

  8. Beamanator commented on Feb 15, 2024

    @Beamanator
    Contributor

    Also demoted #36598 as it's a very minor issue

  9. kavimuru commented on Feb 15, 2024

    @kavimuru

    Regression is at 70%. Unchecked PRs are pending validation.

  10. kavimuru commented on Feb 16, 2024

    @kavimuru

    Regression is 6% left.
    #34080 is failing in mweb chrome with #36597 and repro in PROD checking it off
    #35294 is failing with #36651 in web and repro in PROD checking it off
    #34719 is pending validation in all the platforms but Web
    #35306 is pending validation in Desktop
    #36304 is pending validation in Desktop
    Open blockers:
    #36574
    #36599
    #36603
    #36643
    #36645
    #36646
    #36647

  11. marcaaron commented on Feb 16, 2024

    @marcaaron
    Contributor

    Checking off #36645 as it does not seem urgent

  12. kavimuru commented on Feb 16, 2024

    @kavimuru

    Regression is 1% left.

    #34719 is failing with KI #33540 (reopened the issue) OK to check it off?
    #35306 is failing with #36601
    #36304 is failing with #36602 and repro in PROD checking it off
    Open blockers:
    #36574
    #36599
    #36603
    #36643
    #36646
    #36678
    #36687
    #36695

  13. 4 remaining items

  14. Beamanator commented on Feb 19, 2024

    @Beamanator
    Contributor

    #36599 and #36695 just got fixed by #36631

  15. Beamanator commented on Feb 19, 2024

    @Beamanator
    Contributor

    Checked off #36643 b/c it got closed as expected behavior

  16. chiragsalian commented on Feb 19, 2024

    @chiragsalian
    Contributor

    #34719. Checking it off. From this comment it looks like we're good to proceed.

    @Expensify/applauseleads

    #36705 - it looks like the PR to fix the issue was CP-d. From the checklist the CP'd PR was checked off by @kbecciv so I'm assuming they tested it and it ran well and since it was linked to the issue #36705 which has the same steps as the PR i'm going to check it off the list.

  17. kbecciv commented on Feb 19, 2024

    @kbecciv

    @chiragsalian QA team checked CP #36798 and it passed, checked off.

  18. kbecciv commented on Feb 19, 2024

    @kbecciv

    CP #36810 is Pass, checking off

  19. chiragsalian commented on Feb 19, 2024

    @chiragsalian
    Contributor

    Look like this issue - #36574, has a PR that was CP-d. It looks like you checked off the PR so i guess you tested it. Can you check if that means we're good to check off its issue too i.e., #36574.

    Let me know if there is anything else pending on our end.

  20. kavimuru commented on Feb 19, 2024

    @kavimuru

    @chiragsalian #36574 can be checked off, CP #36810 is validated and it is a pass.
    Only DB is #36678

  21. chiragsalian commented on Feb 19, 2024

    @chiragsalian
    Contributor

    Yup i asked about #36678 in the earlier comment here. We are unable to reproduce it. Can you or someone else retest this to confirm if the issue still persists.

  22. kavimuru commented on Feb 19, 2024

    @kavimuru

    @chiragsalian checking

  23. kavimuru commented on Feb 19, 2024

    @kavimuru

    @chiragsalian not able to reproduce #36678 by the tester who reported and me.
    #36678 (comment)

  24. chiragsalian commented on Feb 19, 2024

    @chiragsalian
    Contributor

    Cool, i checked off #36574 and #36678

  25. chiragsalian commented on Feb 19, 2024

    @chiragsalian
    Contributor

    :shipit:

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions