Repository navigation
Support CONNECT_SERVER_VERSION env var #807
Description
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?
Metadata
Metadata
Assignees
Labels
No labels
Activity
marcosnav commentedon Jun 30, 2026
@nealrichardson Are you going to take this work on or do you want this as part of Intake?
nealrichardson commentedon Jun 30, 2026
Either way is fine with me. This is very Claude-able.
marcosnav commentedon Jul 1, 2026
claude Work on this, introduce the env var lookup approach.nealrichardson commentedon Jul 1, 2026
No at-Claude here, I'll have mine get at this.
marcosnav commentedon Jul 1, 2026
Gah, of course 🤦♂️