In short, yes [1]. Everything always changes all the time.
As much as everyone wishes breakage didn't happen, and as hard as they try, it still does. You'll no doubt "fondly" remember all that happened with the transition from 32-bit x86 to 64-bit [2], or 16-bit to 32-bit for that matter. Over in Apple world, we've gone through several architecture changes. 68K to PowerPC to x86 to Arm. And that's just the Mac family.
There have been some incremental technologies that smooth the transition (software emulation, multi-architecture binaries). But pragmatically, breakage is inevitable.
Does anyone know if any thought has been put into gradually phasing out this cargo misfeature? Hopefully one day it will reject the crate as early as parsing its Config.toml. Ranges can be reasonable, but unbounded > is just a completely illegitimate construct. No one can predict the future.
It's not a new issue: Unexpected dependency resolution when using ">" · Issue #3292 · rust-lang/cargo but I haven't seen any indication that cargo wants to fix it. Any RFCs or open issues tracking this? Should a discussion for deprecating unbounded > be opened on IRLO or Zulip?