Danger warning when an MR might violate multi-version compatibility
The following discussion from !63374 (merged) should be addressed:
-
@DylanGriffith started a discussion: (+5 comments) @cablett please correct me if I'm wrong here but this appears to be an example which violates Multi version compatibility. This MR is using a new field from the frontend and adding that new field in the backend in the same MR. So this could mean that the frontend is sending the query to an older version of the backend during a deployment and therefore these would fail.