Code-default fallback for flags without defaultVariant
AffectsRPC using v2 proto schemas, OFREP, and in-process resolvers
Previously, evaluation returned FLAG_NOT_FOUND; updated paths now use the code default without an error. OFREP represents that fallback as a success response with reason default, omitting value and variant, while the older proto path still returns FLAG_NOT_FOUND.
Evidence“// if reason is fallback, we want to omit the value and variant from the response, and set reason to default” open-feature/flagd/pull/1862 ↗
Show release-note lines
### ⚠ BREAKING CHANGES * no `defaultVariant` -> code default (previosuly FLAG_NOT_FOUND) ([#1862](https://github.com/open-feature/flagd/issues/1862)) * no `defaultVariant` -> code default (previosuly FLAG_NOT_FOUND) ([#1862](https://github.com/open-feature/flagd/issues/1862)) ([89117d8](https://github.com/open-feature/flagd/commit/89117d8eaba0e9d205b3b47544528c42d5698176))github.com/open-feature/flagd/releases/tag/core/v0.14.0