This was published already two minors ago, and migration happens on any write to the schema registry, so I think we can remove the code there in serde_hacks::v1_data_model
If v1 is still detected, we can panic with something along the lines of "go back one version, do any mutation on the schema registry (something as simple as adding a header to a deployment is enough), then update again"
This was published already two minors ago, and migration happens on any write to the schema registry, so I think we can remove the code there in
serde_hacks::v1_data_modelIf v1 is still detected, we can panic with something along the lines of "go back one version, do any mutation on the schema registry (something as simple as adding a header to a deployment is enough), then update again"