I just commit to technologies for long periods of time. I suspect there are very few new frameworks or technologies you've had to move too in recent years or that have provided enough of an improvement over your existing ones to make sense.
The idea of chasing the bleeding edge of tech is a choice. You don't need to make it.
KAPT being replaced with KSP (which breaks a whole bunch of stacks)
We get emails saying hey, you gotta make this change in a few months or we'll be delisting you.
Most of the popular libraries end up being replaced with bits and pieces of Google Jetpack. This is a lot softer, but we've spent weeks just updating dependencies because it breaks things in chains. We've had hours long pair programming sessions trying to debug some abstract error message. You can't replace a small piece, taking one out makes it collapse in strange ways.
The moral is don't expect Google to keep anything consistent (except Gmail I guess). But it also makes for decent job security.
From what I read of the OP they were talking about JS frameworks so it'd be like having to go from Java to Kotlin to Flutter to react mobile every few months not just updating libraries which is annoying but has continuity.
The idea of chasing the bleeding edge of tech is a choice. You don't need to make it.