-
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-11-15 #12753
Comments
🚀 All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/1.2.28-0 🚀 |
Working on internal QA for #12429 - we may need some edits - I've posted a comment on the PR. |
Thanks for taking over QA on that one. Just saw this now |
👏 Heads up @Expensify/applauseleads 👏 |
🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.2.28-1 has been deployed to staging 🎉 |
@roryabraham We are blocked on Desktop due to #12760 |
A fix for #12760 is being CP'd to staging presently |
👏 Heads up @Expensify/applauseleads 👏 |
thanks @roryabraham we will resume |
Confirmed #12760 is resolved, checking it off |
Regression is completed PR #12226 is failing #12777. Repro in PROD |
While they are PROD QA, keep in mind that help pages are deployed immediately so can be QA'd at any time. Usually this will be very quick so for now while we don't have a prodQA checklist we should just do them during the main checklist. There's also no scenario where we'd have a help site deploy blocker, so there's not much risk involved with these.. Confirmed myself that this works so we should be good to check it off.
|
I am seeing a spike in homepage initial render, but it seems probably that this could be attributed to the process change ensuring that people test on high traffic accounts. |
Release Version:
1.2.28-2
Compare Changes: production...staging
This release contains changes from the following pull requests:
Internal QA:
Deploy Blockers:
Deployer verifications:
cc @Expensify/applauseleads
The text was updated successfully, but these errors were encountered: