Releases

flagd core v0.16.0 changes disabled flag evaluation from an error response to a successful resolution with reason=DISABLED, affecting gRPC/OFREP callers and code that inspects evaluation metadata.

• breakingAudit any code that checks errorCode or reason on flag evaluations

  If your code branches on FLAG_DISABLED error codes or checks the reason field from direct gRPC/OFREP responses, it will no longer receive that error path for disabled flags — it'll get a success with reason=DISABLED instead. Search your codebase for FLAG_DISABLED string matches, error-code switch statements, and reason-field conditionals before upgrading. SDK users who only consume the resolved value are unaffected and can upgrade without changes.

• enhancementUse reason=DISABLED for observability and audit logging

  The new behavior is actually cleaner for telemetry. Since disabled flags now resolve successfully, you can distinguish 'flag disabled' from 'evaluation error' in your metrics and logs without special-casing error codes. Update your dashboards and alerting rules to treat reason=DISABLED as an expected, non-error signal rather than filtering it out as noise.

flagd 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.

OpenFeature core/v0.15.8 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature flagd/v0.15.7 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature core/v0.15.7 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature flagd-proxy/v0.9.6 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature flagd/v0.15.6 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature core/v0.15.6 was released, but the published notes are too brief to summarize. See the original release notes for details.

flagd core v0.15.5 fixes evaluation correctness bugs in fractional rollouts and JSONLogic and/or operators — teams relying on complex flag targeting rules should upgrade.

• securityDependency security alerts resolved

  Dependabot security alerts were resolved in this release. No CVEs are called out explicitly, but the dependency updates address known vulnerabilities in transitive deps. Upgrade if you're running flagd in a security-sensitive environment.

• breakingFractional evaluator fix: upgrade if you use targeting keys

  Null or missing targeting keys in fractional evaluators previously caused undefined behavior. If your flag rules use fractional/percentage rollouts and some users may lack a targeting key (e.g. anonymous users), upgrade to avoid incorrect bucket assignments.

• breakingJSONLogic and/or bug fix may change evaluation results

  The jsonlogic and/or operator bug could cause flag rules with compound boolean logic to evaluate incorrectly. Review any rules relying on and/or conditions after upgrading — results may change from what you saw in v0.15.4.

OpenFeature flagd-proxy/v0.9.5 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature flagd/v0.15.5 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature core/v0.15.4 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature flagd/v0.15.4 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature core/v0.15.3 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature flagd/v0.15.3 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature core/v0.15.2 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature flagd-proxy/v0.9.4 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature flagd/v0.15.2 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature core/v0.15.1 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature flagd-proxy/v0.9.3 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature flagd/v0.15.1 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature core/v0.15.0 was released, but the published notes are too brief to summarize. See the original release notes for details.

OpenFeature flagd/v0.15.0 was released, but the published notes are too brief to summarize. See the original release notes for details.