We currently hardcode API version 620. Users can select an older version through the api_version .app environment variable, but newer versions are not allowed. The latest binary release is at 630, and the upcoming 7.0 release will be either 700 or 710.
The tricky bit is that if we hardcode a higher api version, erlfdb will fail to build if a user has an older client library installed. We should have a ./configure type of interrogation to see what version of the client library is installed, and dynamically configure FDB_API_VERSION during the build to match.
The CI system should test for 630 compatibility, but I don't think we should bother with unreleased versions at this time.
We currently hardcode API version 620. Users can select an older version through the
api_version.app environment variable, but newer versions are not allowed. The latest binary release is at 630, and the upcoming 7.0 release will be either 700 or 710.The tricky bit is that if we hardcode a higher api version, erlfdb will fail to build if a user has an older client library installed. We should have a
./configuretype of interrogation to see what version of the client library is installed, and dynamically configureFDB_API_VERSIONduring the build to match.The CI system should test for 630 compatibility, but I don't think we should bother with unreleased versions at this time.
More discussion on this topic in the FDB forums.