Hell, people get broken by OSS ecosystem libraries a lot.
That's why offsite data backups are a really good thing.
PS: google employee, used to work with torne every now and then, but no stake in the conversation anymore.
Browsers are platforms that are as complex as OSes these days. And any bugs or changes in how they work will affect you app if your app is PWA.
- It could be Chrome breaking audio: https://danshumway.com/blog/chrome-autoplay/
- It could be Chrome breaking LocalStorage: this discussion
- It could be Chrome removing support for a web standard that was implemented and shipped: https://www.chromestatus.com/feature/4642138092470272
I'm linking Chrome issues here because Chrome is the most visible of all browsers with the largest marketshare, but other browsers have their issues, too.
There are several polyfills available. Several Polymer versions targeted v0. Etc. etc.
It's not specifically Google's fault that they are removing support for these, but, once again, that's the state of the world: browsers are lrage complex platforms that may and will break your app.
While it's true that browser updates may break your app, it's also true that there are ways to write the app so as to minimize the risk of such breakage. Using Custom Elements V0 was _not_ a good way to avoid potential breakage...
On most consumer OSes I honestly would trust the chrome developers to be more well behaved.