I think that's backwards. Anything that changes the performance of a model deserves a minor version bump. A new model has to be qualified before being pushed to production; but we don't get the choice here, just cross your fingers there are no regressions at all on all possible tasks the model might be asked to do.

That's on you for using a preview/beta. It was properly qualified when it was released. No one complains when ios goes from beta to release; even though it will be ios 27 beta -> ios 27 next month

I should have worded it differently. Having a model selector as `string` seems like the wrong choice. At the very least, I should be able to select 4.X, like how we select dependencies, so people who rely on specific behavior can pin to 4.0 and I can say version >= 4 if I don't care.