[kinyoklion]

Updates the README feature matrix after the OpenFeature Ruby SDK 0.6.6–0.8.1 releases (2026-10-22/23) and LaunchDarkly Ruby SDK 8.19.0.

• Eventing goes from ✅ to ⚠️, listing two provider gaps:
  • A data source update that leaves the provider status unchanged is emitted again (fix in feat: Support waiting indefinitely for initialization #36).
  • The provider relies on SDK-emitted PROVIDER_READY/PROVIDER_ERROR, which OpenFeature Ruby SDK 0.7.0 deprecates (tracked in Emit provider lifecycle events from the provider now that the OpenFeature Ruby SDK supports opting in #39).
• Initialization notes that since LaunchDarkly Ruby SDK 8.19.0 a rejected SDK key is retried, so the constructor waits the full wait time before initialization fails.
• Domains notes that the provider is not domain-scoped (domain_scoped?, OpenFeature Ruby SDK 0.6.7).

Details

• Duplicate events: LaunchDarkly Ruby SDK's DataSourceUpdateSinkImpl#update_status broadcasts again when the state is unchanged but there is a new error. DataSourceStatusListener emits every broadcast, so one INTERRUPTED period can produce several PROVIDER_STALE events (OFP 4.2.2). feat: Support waiting indefinitely for initialization #36 already adds the status de-duplication.
• Deprecation: in OpenFeature Ruby SDK 0.7.0 (feat: let providers own their lifecycle events open-feature/ruby-sdk#353), a provider with init but without emits_lifecycle_events? takes the legacy path, and the SDK logs a deprecation warning once per provider class. The gemspec's ~> 0.6.1 keeps 0.7 out of range today, and fix: Allow openfeature-sdk 0.7 and 0.8 #38 widens it. Emit provider lifecycle events from the provider now that the OpenFeature Ruby SDK supports opting in #39 describes the follow-up and what blocks it: fix: Allow openfeature-sdk 0.7 and 0.8 #38, feat: Support waiting indefinitely for initialization #36, the Bundler cooldown, and a needed OFP 4.2.5 update.
• Rejected key: in 8.19.0 the stream and polling data sources report INTERRUPTED and retry after any failure, and they go to OFF only from stop. @ready is set only on success, so a rejected key keeps the constructor waiting for the full wait_for_seconds.
• Other changes in 0.6.6–0.8.1 need no provider change:
  • Hook inputs are immutable and flag metadata is frozen. The provider builds a new metadata hash on each evaluation.
  • Clients resolve their domain's provider on every call.
  • Isolated API instances are supported. The provider includes EventEmitter, so the SDK rejects registering one instance with two APIs.
  • PROVIDER_RECONCILING/PROVIDER_CONTEXT_CHANGED are static-context events and don't apply to a server provider.
• Docs only, so no changelog entry or release.

Link to Devin session: https://app.devin.ai/sessions/b215bd8a675f4cc39541f1741d4013b7
Open in Devin Desktop: https://app.devin.ai/desktop/session/b215bd8a675f4cc39541f1741d4013b7?variant=devin
Requested by: @kinyoklion

SDK-3423

---

Note

Overview
Updates the README feature matrix to reflect OpenFeature Ruby SDK 0.7.x and LaunchDarkly Ruby SDK 8.19.0 behavior—documentation only, no code changes.

Eventing is downgraded from fully supported to partially supported (⚠️) with notes on two known gaps: duplicate provider events when the data source status stays the same but errors update (#36), and reliance on SDK-emitted init lifecycle events that 0.7.0 deprecates (#39).

Initialization now explains that rejected SDK keys are retried in 8.19.0, so init may block for the full configured wait before reporting failure. Domains clarifies the provider is not domain-scoped, so one provider instance can back multiple OpenFeature domains with a shared LaunchDarkly client.

^{Reviewed by Cursor Bugbot for commit 7cac07d. Bugbot is set up for automated code reviews on this repo. Configure here.}

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring