No, the issue yesterday is that people had to go in manually to fix their CI builds, etc. That's simply not necessary if you don't update the version and yanking is disallowed (which it should be).
After that, if people want to at some point update to a newer version of the package, yes, they will have to adjust.
Hrm, fair point. Although migrating 'backwards-compatibly' like that could leave a lot of people in the cold if-and-when a security update for the package is released (and we're talking about critical packages here, at least for now).
After that, if people want to at some point update to a newer version of the package, yes, they will have to adjust.