Sure, but Discourse is going to change, thats why you get notifications and hit an update button. Upgrades will change aspects of discourse as well as the versions of underlying software components all the time. Outdated plugins which assume older versions of stuff will, in turn, stop working.
I would strongly recommend you test upgrades on a staging site, particularly if you rely on third-party plugins.
Sorry - I’m not here pointing fingers if that wasn’t clear
If the error was a bit more descriptive, I see value in posting in a more active forum along with developers that have changed dependencies and the code base recently. The exposure here is obviously much greater than on a plugin’s GH.
But… a TypeError without a trace is particularly useless will head to GH