So we all believed that the added complexity of @GraphQL would help us get away from breaking api version changes and maintain legacy clients when the backend implementation needed to change. Then you see things like this from @mondaydotcom. Pretty sure thats a fail.

@JavascriptMick @GraphQL Hey Michael, we are sorry to hear of your frustration towards our recent update. We hear where you're coming from and have relayed this to the dedicated team internally. Please feel free to reach out via DM if you have further feedback - your comments are very important to us!