-
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-08-21 #25625
Comments
#23626 this is from previous deploy |
🚀 All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/1.3.56-0 🚀 |
Unlocking this because staging deploys are broken. We hopefully fixed them but need to trigger a full deploy from main. Slack context: https://expensify.slack.com/archives/C03V9A4TB/p1692661899493529 |
New staging deploy running here, re-locking this checklist. |
🚀 All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/1.3.56-2 🚀 |
@roryabraham I went through the list of blockers and categorized them by status to help you out a bit! 🆗 means that the deployblocker label was removed (I checked these off above). ✔️ means that the linked PR was merged (I'm not sure if it's okay to check these off above yet). 📋 means that there is a PR in review but not merged. ❗ means that the issue either has no PR yet or is unassigned. 🆗 #25481 - Likely fixed, deploy blocker label removed |
@roryabraham TR Regression is completed we are wrapping last CPs/PRs Current PR summary |
I checked off #25679 after its PR was cherry-picked and I retested on staging. |
Checking off #25767. The feature is still a WIP, we're aware of it and have a PR in review to fix it. |
We made a fix for #25697, but it looks like that isn't tracked here -- do we need to do anything to get this into staging @roryabraham? |
Checking #25737 off, fixed in staging |
@lindboe there's a known 🐛 that causes cherry-picked PRs to not automatically appear on the checklist. In general you shouldn't need to do anything to have them appear. In this case, I did manually add the fix to the checklist I believe: #25710 |
Checking off #25784. Not repro on main anymore, the feature is still a WIP and the bug doesn't affect App functionality. |
#25649 is a valid bug but not bad enough to block deploy imo. Going to check it off. |
Checking off #25686 since it was demoted to NAB. |
Checking #25616 off its fixed |
Checking off #25676, not reproducible |
checking #25476 off based on this comment #25441 (comment) tested just now |
Demoted #25713, checking it off |
#25718 is fixed, checking it off |
#25728 is fixed, checking it off |
#25705 is fixed, just tested it, checking it off |
#25776 is expected behavior, checking it off |
For #24346, it seems like we don't have deeplinks configured for the routes in question, and it's very unlikely that a first time user will have the app installed anyways. Checking it off |
Checking this off as NAB. @mvtglobally In the future you can feel free to check these off as long as the issue is documented. |
Asked for more details in the PR: #24513 (comment) Going to check this off as NAB, it just doesn't fix the original issue it was meant to fix it seems. |
Demoting #25779. edge case issue imo and not a common flow people would typically be running into. |
#24577 is a QA fail but not a blocker. Left a comment requesting more details in the PR |
#24643 was associated with two issues:
But both are demoted / resolved so I'm going to check off #24643 |
#25399 is a QA fail but not a deploy blocker, checking it off |
As @marcaaron mentioned, #25789 caused another deploy blocker, but we're going to resolve it separately so I'm checking #25789 off |
Demoting #25787 |
Demoting #25803 and checking it off |
#25673 is not reproducible and ultimately a somewhat minor bug that doesn't affect usability. Demoting it and checking it off |
Internal QA on #24637 ✅ |
Release Version:
1.3.56-24
Compare Changes: production...staging
This release contains changes from the following pull requests:
output_name
in fastlane to match up with previous names #24599output_name
key #24600DemoSetupPage
component #24649state_change
event #25158Internal QA:
Deploy Blockers:
DistanceRequest
tab ofMoneyRequest
page #25696Deployer verifications:
cc @Expensify/applauseleads
The text was updated successfully, but these errors were encountered: