Exactly, “breaking” is a variable term, and perhaps too strong a word here, since the 2.3.0 ParamQuantity change (smoothing vs immediate) likely has no effect on 99.99% of plugins. I suspect that VCV deemed the change so minor that it could not have any noticeable effect, and proceeded to do the change, but it so happens that in one of our modules, there was an unforeseen side-effect.
In other words, it’s pehaps hard for VCV to know what all 3000 modules are doing, and as Squinky said, it is indeed not the kind of thing we expect from VCV, but no one’s perfect and software is complex. Perhaps @baconpaul’s solution (5-6 posts up from here) is the best one.
For the record also, it has been said before that when new Rack methods are introduced in minor revisions, if we want to use them in our code, then it is understood that users have to have at least the version of Rack containing that new code, so it’s up to developers to manage this. In the present case though, it was more than this, since to get the former hehavior, we had to use the new methods. But like I said, Paul proposed an intersting workaround that I will explore.