Deploy Checklist: New Expensify 2022-06-09

[OSBotify]

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

This release contains changes from the following pull requests:

• Refactor Graphite_Timer to SendPerformanceTiming #9349

  • QA
  • Accessibility

• Revert "[NO QA] Display report archived text in welcome message as well as footer" #9378

  • QA
  • Accessibility

• [No QA] Clarify who can officially accept proposals #9392

  • QA
  • Accessibility

• fix the breaking of email at close account page #9400

  • QA
  • Accessibility

• [No QA] Fix analyze-packages script #9431

  • QA
  • Accessibility

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.

cc @Expensify/applauseleads

[roryabraham]

@Expensify/applauseleads 🍾 problems – we've got an empty checklist! I guess that's what happens when we do two deploys in a single day 😉 No need to lock it until we have at least one new PR.

In the meantime, a valuable thing to work on (if you're looking to fill your time) would be to review bug fixes over the last few months and evaluate if there are missing edge cases that should be added to the regression test suites.

[SumitDiyora]

Checked all PRs on Production / Staging and created accessibility issues for all PRs where accessibility issues were found.
The non-applicable PRs are - #9349 #9378, #9392, #9431
Logged Issues - #8465, #9463, #8430, #8398, #8393, #8392, #8577

[OSBotify]

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

[mvtglobally]

@roryabraham Regression is completed

Issues logged
#9391
#9403
#9406
#9407
#9436
#9437
#9438
#9439

[roryabraham]

There's a new Android crash, but it's only happened once. I think it's probably a React Native bug, maybe only on Samsung devices (which seem to have a few issues with React Native TextInputs). It's pretty similar to this issue. For now, I think we can just try to monitor the crash and see if it keeps happening or if we can get some reproduction steps for the issue.

[roryabraham]