-
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
[No QA] Update staging from main #4113
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, let's do it.
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
As expected, no staging deploy occurred. The above comment is not 100% accurate, but we don't need to worry about that right now. |
Oof, I think this was backwards 🤦 |
We merged staging into main, not the other way around. That was not what I meant to do... 😓 |
Sorry for the inconvenience @tgolen, but I think now the best thing to do is to create a normal PR to fix the issue on main and then CP it to staging. |
🚀 Deployed to staging in version: 1.0.79-5🚀
|
🚀 Deployed to production in version: 1.0.80-2🚀
|
cc @tgolen
Details
Come from this comment
Fixed Issues
$ #4060
Tests
StagingDeployCash
.QA Steps
No QA.
Tested On
n/a – GitHub only.