Since you work at Google, you should be well aware of the deprecations. You don't need evidence of their existence, you just don't see it as a problem. Which you are free to do, since it's not a problem for you, it's just a problem for GCP clients, many of whose complaints you seem to be dismissing as not being "data".
GCP doesn't seem to provide a full list of deprecations, but the list for just one service[1] is pretty terrifying when you consider that your app might depend on two or three dozen services, and a deprecation in just one of them forces you to rewrite perfectly good code. A cursory search reveals a number of reports of being repeatedly bitten by deprecations[2][3][4], so no one should be mislead by the dismissals here. [2] has a good cautionary tale of a forced "upgrade" leading to potentially much greater cost.
I do work at Google: I’m not trying to dismiss the concerns and I understand that deprecations are a legitimate concern and carry a significant business cost. It sucks that you got burned a few years ago, and I totally get the why you lost trust in GCP.
I do think Google Cloud is trying to do better and the few deprecations I’ve seen personally have been heavily scrutinized and considered, with a clear migration path for users. I was only asking for data to objectively understand the problem as it stands today, and not to minimize your own experience. I know there are experiences similar to yours, but hopefully there are far fewer in recent years (but its always hard to tell without data).
I do think Google Cloud is trying to do better and the few deprecations I’ve seen personally have been heavily scrutinized and considered, with a clear migration path for users. I was only asking for data to objectively understand the problem as it stands today, and not to minimize your own experience. I know there are experiences similar to yours, but hopefully there are far fewer in recent years (but its always hard to tell without data).