My team came across this today after testing code that already worked before. We found a way to stop it from breaking our code. Our questions are, should we expect this to keep happening and can another integration data come across with this call?
I guess "should" is a matter of opinion. Generally, users will want the widest set of info returned, but when you are strictly validating the JSON response (I assume that's what happened to you) that causes a problems. There were other regressions (or shall we say "failed progressions") in the latest API release that are driving us up the wall as well.