-
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-10-05 #11623
Comments
🚀 All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/1.2.12-0 🚀 |
Checking off #11318 since it was solved yesterday, but we reopened the issue to pay the reporting bonus to the contributor. |
👏 Heads up @Expensify/applauseleads 👏 |
🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.2.12-1 has been deployed to staging 🎉 |
👏 Heads up @Expensify/applauseleads 👏 |
🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.2.12-2 has been deployed to staging 🎉 |
Regression is completed PR #10967 is Blocked on mWeb due to #7270 |
Checking #11654 (comment) off as it was aslo repro in production so no deploy blocker. |
Since #11632 is not reproducible, then yes lets check off #11371 |
#11669 doesn't look to be a blocker and is expected functionality |
So #11631 should be good in that case! |
QA'ed #11538 by uploading a corrupted PDF file, and it seemed to work fine, so checking it off. |
Ok we got this down to two last items!
@MariaHCD and @Justicea83 Can you please treat this with priority, we would love to deploy on Monday in the morning PST time! 🚀 |
This was already checked off, but #11226 is not a blocker. We can not reproduce . If an additional step is required in order to reproduce, then it should be raised as a separate issue as the original test steps work as expected. |
Update regarding #7270 is here: #7270 (comment) |
@Expensify/applauseleads - Can you retest #11533 please? |
@AndrewGable checking |
@AndrewGable Can you confirm the build we should be checking for #11533 ? It seems to be still giving an error on 1.2.12-2 |
This error I believe seems different, it was fixed on the backend so |
@AndrewGable We only have Fidelity working right now. I will check with the team if they were able to add any other type. But if not, this may need to be validated internally |
👏 Heads up @Expensify/applauseleads 👏 |
Agree that's a different error. I think the product in the screenshot above is working as designed. |
Checked off #11533 with @JmillsExpensify confirmation. Checked off #10967 since it was reverted and CP-ed. |
@AndrewGable thanks for confirmation. We are down to 2 Blockers |
🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.2.12-3 has been deployed to staging 🎉 |
Thank you @mvtglobally - We are working on a fix |
@AndrewGable hopefully we can get a new deploy today. pls tag us if anything needs retests |
👏 Heads up @Expensify/applauseleads 👏 |
|
🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.2.12-4 has been deployed to staging 🎉 |
Release Version:
1.2.12-4
Compare Changes: production...staging
This release contains changes from the following pull requests:
GetRequestCountryCode
#11369shouldShowComposeInput
to it's own key #11434currentlyViewedReportID
#11450participants
list when creating new workspace room #11475ActivateStep
component #11489Deploy Blockers:
Deployer verifications:
cc @Expensify/applauseleads
The text was updated successfully, but these errors were encountered: