Spec v0.9.0 compliance #300

Activity

1. toddbaert

   added

   v0.9.0spec v0.9.0 compliancespec v0.9.0 compliance

   OpenFeature specificationhaving to do with implementation of and/or deviation from https://openfeature.dev/specification/having to do with implementation of and/or deviation from https://openfeature.dev/specification/

   on Jul 29, 2026
2. josecolella commented on Oct 22, 2026

   

   josecolella

   on Oct 22, 2026

   Collaborator

   More actions

   Progress update and a few scope changes after an audit against v0.9.0:

   • Landed or open: chore: pin spec submodule to v0.9.0 #335 (spec pinned to v0.9.0) and docs: fix README timeout example and stale requirement IDs #336 (stale requirement IDs) are merged. Open for review: feat: add PROVIDER_RECONCILING and PROVIDER_CONTEXT_CHANGED events #338 (RECONCILING and CONTEXT_CHANGED events), fix: carry provider error codes through hooks #339 (provider error codes), feat: support variant flags in InMemoryProvider #340 (variant flags in InMemoryProvider; gherkin now runs on it, per Appendix A) and fix: detach replaced and shut-down providers #341 (detach replaced providers).
   • Telemetry: Appendix D is guidance, and Telemetry.create_evaluation_event already matches the v0.9.0 attributes. The remaining gaps (error.type, error.message, recording exceptions in the error stage) are in contrib's OTel hook, so I'm moving that item there.
   • Multi-provider: deferred to its own follow-up after this release.
   • New items found in the audit:
     • Clients capture their provider at build time, so rebinding or shutting down a provider doesn't reach existing clients (1.1.3, 1.7.1).
     • Replaced providers are never detached, so their events still reach handlers (1.6.2, 2.5.2); fix: detach replaced and shut-down providers #341 fixes this.
     • Client handlers that emit events or add/remove handlers raise ThreadError (5.1.2, 5.2.7).
   • Release: maintainers, please hold the release-please PR until the v0.9.0 badge PR merges, so everything ships together as 0.7.0.
3. josecolella commented on Oct 22, 2026

   

   josecolella

   on Oct 22, 2026

   Collaborator

   More actions

   Progress update:

   • Merged: chore: pin spec submodule to v0.9.0 #335, docs: fix README timeout example and stale requirement IDs #336, feat: add PROVIDER_RECONCILING and PROVIDER_CONTEXT_CHANGED events #338, fix: carry provider error codes through hooks #339, feat: support variant flags in InMemoryProvider #340 and fix: detach replaced and shut-down providers #341. 0.6.6 shipped with the last four.
   • Open for review: docs: fix README event handler example and document new events #343 fixes the README event handler example and documents the new events.

   Still open for v0.9.0

   • Supply the bound domain to provider initialization #297: pass the bound domain to provider init. feat(core): pass bound domain to provider init and enforce domain-scoped binding #298 is a draft with merge conflicts.
   • Isolated API instances. API is still a singleton.
   • Provider lifecycle event ownership. There's no opt-in marker yet, and the SDK still emits READY/ERROR after init.
   • Clients keep the provider they were built with, so rebinding or shutting down a provider doesn't reach existing clients (1.1.3, 1.7.1). Reproduced on main.
   • A client event handler that adds or removes a handler fails with deadlock; recursive locking. The SDK logs the error, so callers never see it (5.1.2, 5.2.7). Reproduced on main.
   • Reentrant provider events reach client callbacks out of order #332: event delivery order when a handler emits another event.
   • The OTel hook follow-up (error.type, error.message, recording exceptions) still needs an issue in ruby-sdk-contrib.

   Related: #270–#273 are open spec fixes that aren't on this list yet.

   The specification badge stays at v0.8.0 until the items above land.
4. josecolella commented on Oct 23, 2026

   

   josecolella

   on Oct 23, 2026

   Collaborator

   More actions

   Taking over the remaining items. New PRs and issues:

   • feat: pass the bound domain to provider init and support domain-scoped providers #345 (draft) passes the bound domain to provider init and supports domain-scoped providers. It takes over feat(core): pass bound domain to provider init and enforce domain-scoped binding #298 and keeps Jonathan's commits. Closes Supply the bound domain to provider initialization #297.
   • fix: return defaults instead of raising from client calls #346 (draft) makes client calls return the default instead of raising (1.4.10, 1.4.11).
   • Multi-Provider in the SDK (spec Appendix A) #344 tracks Multi-Provider (Appendix A), deferred until after this release.
   • OTel hooks: align error attributes and exception recording with spec Appendix D ruby-sdk-contrib#268 tracks the OTel hook's Appendix D alignment, moved from here.

   Next up, stacked on #345:

   • event ordering and handler locking (Reentrant provider events reach client callbacks out of order #332)
   • provider-owned lifecycle events
   • clients that look up their provider on every call
   • isolated API instances

   After those: read-only hook inputs (after #273), a compliance pass, and the v0.9.0 badge. Everything ships together as 0.7.0.
5. josecolella

   closed this as completedin #362on Oct 23, 2026
6. josecolella commented on Oct 23, 2026

   

   josecolella

   on Oct 23, 2026

   Collaborator

   More actions

   Closed by #362. Every box above is done, and the README now claims spec v0.9.0.

   Releases: this work shipped across 0.6.6, 0.6.7, 0.7.0, 0.7.1 and 0.8.0. The first release with the compliance fixes (#361), the added tests (#360) and the badge (#362) is 0.8.1, which is still pending in #363.

   Compliance: an audit checked every requirement in sections 1–6 and Appendix A against spec v0.9.0, reading each test's body rather than its label. #362's description has the summary:

   • which requirements fix: close the spec v0.9.0 gaps the compliance audit found #361 fixed and which test: cover spec v0.9.0 requirements the audit found untested #360 added tests for;
   • the n/a reasons, for static-context conditions, generics and finally;
   • how the SDK reads 1.4.10:
     • a wrong-type default raises ArgumentError;
     • exceptions outside StandardError and NotImplementedError propagate.

   Not met, at SHOULD level only:

   • 1.4.12, async evaluation.
   • 1.4.11, partially met.
   • 1.8.4, which is detected only for providers that include EventEmitter.

   Deferred:

   • Multi-Provider: Multi-Provider in the SDK (spec Appendix A) #344.
   • Gaps in the contrib OTel hook: OTel hooks: align error attributes and exception recording with spec Appendix D ruby-sdk-contrib#268.
   • Contrib providers freezing their ProviderMetadata, so hooks don't copy it on every evaluation. There's no issue for this yet.

   Thanks to Cristian Marta (#270–#273, carried in #355 and #358), Jonathan Norris (#298, carried in #345) and Leo Romanovsky (#332, fixed in #351). Each is credited as co-author on the merged commits.
7. josecolella

   self-assigned this

   on Oct 24, 2026