I was blindly sure that we consult API about the version of the schema it expects, but apparently I was wrong since I cannot find any trace of that!?
/info endpoint, e.g. https://api-staging.dandiarchive.org/api/info/?format=json provides schema_version. dandi-cli should not even attempt upload if the schema version it uses doesn't match exactly ATM (I would prefer allowing for higher .patch being allowed, but I think neither dandischema nor dandi-api support that ATM, ref: e.g. dandi/dandi-schema#22 )
I think absence of such prevention mechanism is what resulted in e.g. #719
I was blindly sure that we consult API about the version of the schema it expects, but apparently I was wrong since I cannot find any trace of that!?
/infoendpoint, e.g. https://api-staging.dandiarchive.org/api/info/?format=json providesschema_version.dandi-clishould not even attempt upload if the schema version it uses doesn't match exactly ATM (I would prefer allowing for higher .patch being allowed, but I think neither dandischema nor dandi-api support that ATM, ref: e.g. dandi/dandi-schema#22 )I think absence of such prevention mechanism is what resulted in e.g. #719