They can have version constraints but not all of them do. Without counting, with a quick scan through the topics, roughly a third to half of the entries do not have versioning in the title and it’s that versioning that represents those constraints.
For example, Roborock binding for robot vacuum cleaners [5.0.0; 5.0.99] is indicating it works for all versions of OH 5.0 where as Danfoss Ally Cloud Binding is unconstrained.
I want to make sure everyone knows I’m not advocating for this behavior. I think that the marketplace add-ons should be reinstalled or at least attempted to be reinstalled and errors in the logs if there is a failure.
But to answer the question, that can work only if the bundle actually indicates which versions it supports. For the unconstrained bindings we can’t know what version it supports. So special handling needs to be done in those cases. And there may not be a version that supports the new OH version that was just installed so that too needs special handling.
I think the overall problem is solvable.
I know @Nadahar did some work to make it so one post could post multple builds, one for each version, but I think that never got merged. That work might be relevant here as well.