OpenFeature
flagd/v0.16.0CI/CD & App Deliveryflagd v0.16.0 changes disabled flag evaluation from an error to a successful resolution with reason=DISABLED, affecting direct gRPC/OFREP callers and code that inspects evaluation metadata.
breakingAudit error-handling code that checks FLAG_DISABLED or errorCode
If your application checks the evaluation reason or error code after a flag resolution — whether through direct gRPC calls, OFREP HTTP calls, or Go imports of core/pkg/model — you need to update that logic. FLAG_DISABLED errors will no longer appear; instead expect a successful response with reason=DISABLED. SDK users who only read the resolved value are unaffected, but any monitoring, alerting, or branching logic that keys off FLAG_DISABLED will silently stop triggering. Grep your codebase for FLAG_DISABLED and errorCode checks before upgrading.
主な変更 (4)
- Disabled flags now return reason=DISABLED with a successful resolution instead of a FLAG_DISABLED error code
- Resolved values are unchanged — SDKs still surface the caller-provided default, so end-user behavior is identical
- Breaking impact is narrow: only affects consumers inspecting reason/errorCode, direct gRPC/OFREP callers, or code importing core/pkg/model
- An Architecture Decision Record (ADR) documents the rationale for this semantic change