enamel microversion error response does not follow spec
cdent opened this issue · comments
There's a pending spec on how the body of a 406 response to an invalid microversion should look. It states there should be a json object which describes the min and max available versions.
The format is still up for debate, but I wanted to get our lack written down.