1: We made something that we think is good, but we don‘t know if others will and how they will use it. We tested it well in one scenario but not much else.
2. Now we actually understand how people use this and why they like it. We have collected all of their biggest problems and it‘s time to fix them.
3. Everyone loves our thing and it‘s very productive for them. That must mean we‘re geniuses. Let‘s fuck around and change the world.
4, 5, 6… Both we and our users understand that sometimes we need to make a breaking change. They already went through the terrible 2->3 migration so every other upgrade will be fine by comparison.
In an enterprise context there are probably enough layers that keep everyone in check so the step 3 where you run wild with your ideas never happens.
Although TBH it's not all bad; all anybody has ever really cared about is "are there breaking changes or not?"
React sets a pretty good example here: react 17 is the most boring release in the world. The react team are not bad API designers that made 17 major mistakes. They may be the most considerate and pleasant API designers in all of frontend, actually.
React Native is on 0.64.4 (?) not because it‘s unfit for production but because they know the level of guarantees they can make about version upgrades is zero.