OK, I know I should have refrained from updating just before my bedtime. This happened:
I still have that window open (is the journal useful?) but the rest of the site seems down 
.
Is this the moment to hit that red button which brings up a warning that this is a “last resort” thing to do?
If it’s still working, and I bet it is, just go to bed.
Tomorrow you can do a command line upgrade.
this doesn’t sound very promising:
Your Ruby version is 3.3.8, but your Gemfile specified ~> 3.4
Docker Manager: FAILED TO UPGRADE
I tried ask.discourse after posting and it suggests doing a full rebuild:
sudo git pull
sudo ./launcher rebuild app
yay or nay?
Yeah, GUI updates can occasionally fail for various reasons, and the typical next step is a command line rebuild. In my experience that’s always cleared things up.
(And the sudo on those commands assumes you’re not logged in as the root user.)
I rebuilt, and it’s working new, phew! Was scary. 
Sound familiar @pfaffman ?
Just writing this for the visitors who will read this topic after having themselves issues with the GUI update:
True, it seems more reliable nowadays, but I had enough issues with it in the past to often prefer using the command-line instead, even if it’s less straightforward.
If your update from the interface didn’t work, ./launcher rebuild app from the command line is very likely going to repair it, and there’s no reason why it would result in data loss. It’s safe to use.
Happy Discoursing!
In my experience, the big useless button.
That’s why I built a dashboard.literatecomputing.com that will do the command line rebuilds with a click
