-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy Checklist: New Expensify 2022-09-26 #11297
Comments
🚀 All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/1.2.7-1 🚀 |
#10899 passed internalQA, checking it off |
👏 Heads up @Expensify/applauseleads 👏 |
🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.2.7-2 has been deployed to staging 🎉 |
@mvtglobally #11301 should be fixed by #11303 in |
#11305 is fixed, checking it off |
I was able to verify that #11301 is fixed, checking it off |
Going to work on QA of #11254 |
#11254 seems to be a pass. Performance metrics look good. The only thing is that there's a new crash: https://console.firebase.google.com/u/0/project/expensify-chat/crashlytics/app/android:com.expensify.chat/issues/193757d9bc1c3c9fab13ef0737f6db59?time=last-seven-days&sessionEventKey=6333322C01C900010EA52FBC6C7CF095_1726557865424712073 |
The crash seems like a memory leak problem in React Native itself. Going to ignore for now because I don't think there's much we can do about it, but we'll monitor it and hopefully see an issue created if it persists. |
Release Version:
1.2.7-2
Compare Changes: production...staging
This release contains changes from the following pull requests:
SignInUser
#10811ReportActionItem
#11256report
instead ofreportID
toReportActionItem
#11303Internal QA:
Deploy Blockers:
Deployer verifications:
cc @Expensify/applauseleads
The text was updated successfully, but these errors were encountered: