-
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
[HOLD for payment 2024-11-21] Deploy Checklist: New Expensify 2024-11-11 #52320
Comments
🚀 All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/9.0.60-0 🚀 |
Demoted #52369 |
Regression is 3% left Unchecked PRs: |
Demoting #52367, appears to be fixed on v9.0.60-2 |
Regression is completed. |
We just CP'ed a PR that fixes a lot of blockers, going through them now and will update if issues are confirmed fixed #52342 confirmed fixed on staging - checking #50783 |
All blockers resolved, checking dashboards and this should be ready to close. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.60-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-11-20. 🎊 For reference, here are some details about the assignees on this issue:
|
There's no payment needed here Melv! |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.61-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-11-21. 🎊 For reference, here are some details about the assignees on this issue:
|
Release Version:
9.0.60-3
Compare Changes: production...staging
This release contains changes from the following pull requests:
maxExpenseAmountNoReceipt
tomaxAmountNoReceipt
for policy… #52058assetlinks.json
#52184Internal QA:
Deploy Blockers:
Deployer verifications:
cc @Expensify/applauseleads
Issue Owner
Current Issue Owner: @joekaufmanexpensifyThe text was updated successfully, but these errors were encountered: