SDK Compatibility
Some Featureflow features require a minimum SDK version. Using an older SDK with a newer feature doesn't error — it just silently ignores the capability. For example, an SDK older than the versions below will still evaluate a feature with a JSON-configured variant correctly (you'll get the variant key back as normal), it just won't have a method to read the JSON payload.
Always check this table before relying on a feature in production if you're not certain your SDKs are current.
Feature Compatibility Matrix
| Feature | Node.js SDK | JavaScript SDK | React SDK | Java SDK | Go SDK | Python SDK | Ruby SDK | .NET SDK | React Native SDK |
|---|---|---|---|---|---|---|---|---|---|
| JSON Configuration Values | >= 0.7.0 | >= 2.2.0 | >= 2.2.0 | >= 1.3.1 | Not yet supported | Not yet supported | Not yet supported | Not yet supported | Not yet supported |
Checking Your Installed Version
# Node.js
npm list featureflow-node-sdk
# JavaScript / React
npm list featureflow-client react-featureflow-client
# Java (Maven)
mvn dependency:tree | grep featureflow-java-sdk
If you're below the minimum version for a feature you want to use, upgrade the SDK first — see each SDK's installation instructions for the latest release.
This table only covers SDKs, not the Featureflow platform itself — features gated by SDK version are already live on the server side; the SDK version only determines whether your application code can read the new data.