Open nayib-jose-gloria opened 1 year ago
Publish on mismatched schema versions is already disabled on the backend. This ticket is for rendering a warning to nicely inform Curators of this constraint on the Frontend should the situation arise in their private Collection. It will be tackled, but I don't see it as blocking for migration and can happen in parallel or as a fast follow-up. We can make it blocking if product disagrees
@jahilton - any concerns?
none
Disable Publish button in UI + render a warning if a private collection has dataset(s) with datasets that have mismatching schema_versions (i.e. 3.1.0 and 3.0.0 datasets uploaded)