Breaking change/compatibility documentation?

[nettlep]

Starting with version 16.7.9, using balena-cli produces an error failing to connect to endpoint /actor/v1/whoami.

I found the error was caused by a breaking change that was introduced into balena-sdk (b82bfb5). The commit comment clearly states that this is a breaking change, which is helpful. From this, I was able to downgrade my cli to get back up and running. Finding this was unintuitive and required a bit of sleuthing through depos toI find the root cause. (Googling the error was not very helpful.)

Let's be clear: this is my own fault. I'm on an older version of the open-balena API from last year. I couldn't find a way to determine the API version other than to look at the VERSION file of the running API container, which shows v0.209.2. I realize I need to upgrade, but everything has been working and my priority is developing my iOT devices.

My questions are:

1. Is there a way to determine the versions of the various back-end components (api, haproxy, vpn, registry, etc.)? I was expecting something akin to balena info but I couldn't find any commands in the CLI to do this.
2. Is there any documentation that covers version compatibility between OS, CLI and API? I've seen random bits of this information scattered about various support forums, but nothing official and nothing covering CLI/API compatibility versions.

I understand open-balena relies on some amount of volunteer work, and I'm very appreciative of the work y'all do. This isn't a complaint, just trying to get a better understanding.