fix!: fix valueHasUri bad values and missing types (DEV-1036) #2079
@subotic this isn't breaking change, because it's just plugin to fix bad data. There will be no major version increase, therefore ontology version wasn't updated too. I checked locally
@mpro7 AFAIK there is no way of running the upgrade scripts manually. So the only way is to bump the ontology version number, which then necessitates to bump the mayor number of DSP-API. I think that at some point I said, that each time an upgrade script needs to be run it is seen as a breaking change, because without the upgrade script, the system is broken, which is exactly the state in which we are now. Also, we define what breaking change means. It serves a purpose. In this case, it should scream at the person who is deploying: "look at the logs to see if the upgrade went through without problems" and "this time deployment will take longer than usual".