It should have printed a warning about exactly that. You could then restart the container with
./launcher start app
And then figured out your next steps more leisurely.
You may still be able to start the container.
But to answer the question in the title, not really. This was a big change and there were notifications here about it. Periodically things need upgrading that are external to the stuff that is just the discourse source code that can be upgraded in the ux.