You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PR #8980 is failing due to #9158. Pls double check if it needs to be a blocker as experiences between PROD and Staging differs.
PR #9138 is failing due to #9159
After looking into 9158 it seems to be a regression, but this has been on prod for a few weeks now -- so is unrelated to this checklist. I've posted here and here to ensure we figure out a fix.
After looking into 9158 it seems to be a regression, but this has been on prod for a few weeks now -- so is unrelated to this checklist. I've posted here and here to ensure we figure out a fix.
Just to clarify. I was mistaken here. THIS is the PR which I believe introduced the issue so I've made it a deployBlocker.
Checked all PRs on Production / Staging and created accessibility issues for all PRs where accessibility issues were found.
The non-applicable PRs are - #9136, #9146
Logged Issues - #8403, #8401, #8400, #8413, #8402, #8388, #8387, #8579, #8624
Activity
mvtglobally commentedon May 24, 2022
@Julesssss , its been a while and IOS build still not available. Can you check if it is looking ok?
OSBotify commentedon May 24, 2022
🚀 All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/1.1.66-1 🚀
mvtglobally commentedon May 25, 2022
@Julesssss Regression is completed
Deploy blockers logged
#9159
#9161
#9166
PR #8980 is failing due to #9158. Pls double check if it needs to be a blocker as experiences between PROD and Staging differs.
PR #9138 is failing due to #9159
Issues logged
#9157
#9158
#9162
#9164
Julesssss commentedon May 25, 2022
Checked off 9159 which we believe should be expected after changes in other PRs.
Julesssss commentedon May 25, 2022
Commented on 9161 as I have a feeling this is expected.
Julesssss commentedon May 25, 2022
Additionally, I think 9166 has the same explanation as 9159 and is expected. But I'll await a second opinion before removing the label.
mvtglobally commentedon May 25, 2022
@Julesssss, thanks for update. Hopefully we can have a new deploy today. Let us know if anything needs to be re-tested
Julesssss commentedon May 25, 2022
After looking into 9158 it seems to be a regression, but this has been on prod for a few weeks now -- so is unrelated to this checklist. I've posted here and here to ensure we figure out a fix.
Julesssss commentedon May 25, 2022
Checking of 9161 and 9166 and as discussed in the issues and in Slack.
Julesssss commentedon May 25, 2022
Also checked off 9146 as there is no QA to be performed.
Julesssss commentedon May 25, 2022
Checking off 9138 as the tests pass and we deemed the linked issue to not be a deployBlocker.
Julesssss commentedon May 25, 2022
Just to clarify. I was mistaken here. THIS is the PR which I believe introduced the issue so I've made it a deployBlocker.
chiragsalian commentedon May 25, 2022
I'm checking off
chiragsalian commentedon May 25, 2022
SumitDiyora commentedon May 27, 2022
Checked all PRs on Production / Staging and created accessibility issues for all PRs where accessibility issues were found.
The non-applicable PRs are - #9136, #9146
Logged Issues - #8403, #8401, #8400, #8413, #8402, #8388, #8387, #8579, #8624