Skip to content

Deploy Checklist: New Expensify 2023-07-05 #22282

Closed

Description

@OSBotify

Release Version: 1.3.37-7
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 Jul 5, 2023

    @OSBotify
    ContributorAuthor

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

  2. mvtglobally commented on Jul 6, 2023

    @mvtglobally

    #21962 is failing with #21678 . Checking off

  3. self-assigned this
    on Jul 6, 2023
  4. Julesssss commented on Jul 6, 2023

    @Julesssss
    Contributor

    Closed #22302 as a dupe of #22289

  5. Beamanator commented on Jul 6, 2023

    @Beamanator
    Contributor

    Checking off #21874 since it got reverted in #22303

  6. Julesssss commented on Jul 6, 2023

    @Julesssss
    Contributor

    #22289 was fixed by this PR, which I am about to cherry-pick

  7. Julesssss commented on Jul 6, 2023

    @Julesssss
    Contributor

    Checked off #22297 because it is not a blocker and also isn't always reproducible

  8. mvtglobally commented on Jul 6, 2023

    @mvtglobally

    @Julesssss seeing comments about CPs, but checklist is not updating. Can you pls tag me if we need to QA any specific CPs

    Regression is at 60% complete. still running through TC and PRs

  9. Julesssss commented on Jul 6, 2023

    @Julesssss
    Contributor

    Yeah, I think this is going to be a persistent problem in the short-term. I'll update once the build is complete.

    And to clarify, are these the manual steps we should be doing to make your job simpler?

    • Bump the version after the build is available
    • Add the Cherry-picked PR to the bottom of the checklist
    • Add a comment to document the change
  10. deleted a comment from melvin-bot on Jul 6, 2023
  11. Julesssss commented on Jul 6, 2023

    @Julesssss
    Contributor
  12. Julesssss commented on Jul 6, 2023

    @Julesssss
    Contributor

    #22308 was also resolved by the #22323 CP

  13. Julesssss commented on Jul 6, 2023

    @Julesssss
    Contributor

    Checking off #22340 as it's not worth blocking the release on. A fix PR was just merged, but CPing it feels unnecessary due to the low importance and the delay it adds (preventing me from a hypothetical release this afternoon)

  14. Julesssss commented on Jul 6, 2023

    @Julesssss
    Contributor
    • Located one new Android exception that might have been introduced here. It's a wild guess though and is not a blocker
    • No new iOS exceptions 🎉
    • Timing looks nominal
  15. mvtglobally commented on Jul 7, 2023

    @mvtglobally

    Regression is completed

    #20186 is repro old KI while validating #16696. Checking off
    #21312 is repro old KI #20370. Checking off
    #21857 (comment)

  16. Julesssss commented on Jul 7, 2023

    @Julesssss
    Contributor

    Checking off two blockers (22351 & 22183), with the introduction of these PRs:

  17. Julesssss commented on Jul 7, 2023

    @Julesssss
    Contributor

    Checked off #21857 👍

    The final CP has been completed and I'm now reviewing the CP'd PRs myself manually (everything at bottom of the PRs list)

  18. Julesssss commented on Jul 7, 2023

    @Julesssss
    Contributor

    I finished checking off the CP'd fixes and re-ran the developer verififications ✅

  19. Julesssss commented on Jul 7, 2023

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