See #805 (comment). It is possible (though I wouldn't recommend!) to suppress the Connect server version from the server_settings endpoint, which means that checks for feature availability based on the Connect server version can't know what the version is, and so they default to "off".
What if, in the checks for minimum Connect version, we fell back to an env var lookup, so that if you know it is safe to use a feature even if your Connect server suppresses it, you can tell the library to act as if CONNECT_SERVER_VERSION is the version it is talking to?
See #805 (comment). It is possible (though I wouldn't recommend!) to suppress the Connect server version from the
server_settingsendpoint, which means that checks for feature availability based on the Connect server version can't know what the version is, and so they default to "off".What if, in the checks for minimum Connect version, we fell back to an env var lookup, so that if you know it is safe to use a feature even if your Connect server suppresses it, you can tell the library to act as if
CONNECT_SERVER_VERSIONis the version it is talking to?