-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 2023-12-19 #33264
Comments
🚀 All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/1.4.14-0 🚀 |
yes!
nope @mvtglobally thanks for asking for confirmation |
Checking off #33283 as its expected behaviour |
Checked off #33291 following revert of PR and retest |
@Julesssss @jasperhuangg we are blocked with Android at the moment. If you could prioritize that Blocker would be great |
Closing blocker #33313, backend fix was CP'ed to staging and confirmed working. |
@mvtglobally We merged a revert of the offending PR that was causing the crash, I'll let you know as soon as it has been deployed to staging. |
@mvtglobally can you update your Android builds and let me know if they're still crashing? |
@jasperhuangg asking |
Are we testing the build 1.4.14-1? |
@mvtglobally we are testing |
Checking off #33284 NAB |
@mvtglobally I think it should be deployed now, can you check if the crash still happens? |
Checked off #33277 as the PR that introduced the issue has been reverted |
Regression is completed OPen Blockers. PRs |
Checking off #33290, CP'd a fix |
Checking off #33314 NAB |
Checking off #33348 NAB |
Closing #33354, fix was CP'd |
CP'd fix for #33358, checking off |
Checking off #33367 CP'd fix |
This issue either has unchecked items or has not yet been marked with the |
📣 @os-botify[bot]! 📣
|
Release Version:
1.4.14-6
Compare Changes: production...staging
This release contains changes from the following pull requests:
Deploy Blockers:
Deployer verifications:
cc @Expensify/applauseleads
The text was updated successfully, but these errors were encountered: