From ed74870c09742940dffdda973e04ed6541704d2c Mon Sep 17 00:00:00 2001 From: Leo Romanovsky Date: Mon, 22 Jun 2026 21:17:03 -0400 Subject: [PATCH 1/2] Document Ruby OpenFeature runtime recommendation --- content/en/feature_flags/server/ruby.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/en/feature_flags/server/ruby.md b/content/en/feature_flags/server/ruby.md index 0c18b29ed5a..46a034ac9fb 100644 --- a/content/en/feature_flags/server/ruby.md +++ b/content/en/feature_flags/server/ruby.md @@ -30,10 +30,12 @@ Before setting up the Ruby Feature Flags SDK, ensure you have: - **Datadog Agent** version 7.55 or later with [Remote Configuration][1] enabled - **Datadog [API key][4]** configured on the Agent - **Datadog Ruby SDK** `datadog` version 2.24.0 or later -- **OpenFeature Ruby SDK** `openfeature-sdk` version 0.5.1 or later if you need flag evaluation metrics support +- **Ruby runtime** version 3.1 or later to use the full Datadog Feature Flags OpenFeature integration +- **OpenFeature Ruby SDK** `openfeature-sdk` version 0.5.1 or later for provider hooks, exposure logging, and flag evaluation metrics support - **Service and environment configured** - Feature flags are targeted by service and environment - **Supported operating system** - Production support is limited to [Linux operating systems][2]. macOS and Windows are not natively supported production targets, but Dockerized Linux environments running on those operating systems are. For local development on macOS, you can use a compatible prebuilt native artifact when one is available. +
The Datadog Ruby tracer supports older Ruby runtimes for APM. For Datadog Feature Flags through OpenFeature, use Ruby 3.1 or later because the OpenFeature Ruby SDK versions that expose the provider hook surface required for complete Feature Flags telemetry require Ruby 3.1 or later.
## Installing and initializing From 510d3ab7c95dba0e43baec708773226faff247d5 Mon Sep 17 00:00:00 2001 From: Leo Romanovsky Date: Mon, 22 Jun 2026 21:31:33 -0400 Subject: [PATCH 2/2] Clarify Ruby OpenFeature runtime limit --- content/en/feature_flags/server/ruby.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/feature_flags/server/ruby.md b/content/en/feature_flags/server/ruby.md index 46a034ac9fb..4a6742b2641 100644 --- a/content/en/feature_flags/server/ruby.md +++ b/content/en/feature_flags/server/ruby.md @@ -35,7 +35,7 @@ Before setting up the Ruby Feature Flags SDK, ensure you have: - **Service and environment configured** - Feature flags are targeted by service and environment - **Supported operating system** - Production support is limited to [Linux operating systems][2]. macOS and Windows are not natively supported production targets, but Dockerized Linux environments running on those operating systems are. For local development on macOS, you can use a compatible prebuilt native artifact when one is available. -
The Datadog Ruby tracer supports older Ruby runtimes for APM. For Datadog Feature Flags through OpenFeature, use Ruby 3.1 or later because the OpenFeature Ruby SDK versions that expose the provider hook surface required for complete Feature Flags telemetry require Ruby 3.1 or later.
+
The Datadog Ruby tracer supports older Ruby runtimes for APM. Applications on older Ruby versions, including Ruby 2.5, can continue to use Datadog APM, but cannot use Datadog Feature Flags through OpenFeature until they upgrade to Ruby 3.1 or later. The OpenFeature Ruby SDK versions that expose the provider hook surface required for complete Feature Flags telemetry require Ruby 3.1 or later.
## Installing and initializing