chore(deps): bump dev.openfeature:sdk to 1.22.0 - #197
Merged
Conversation
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
JamieSinn
approved these changes
Aug 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
dev.openfeature:sdkfrom 1.14.2 to 1.22.0 (one line inbuild.gradle)Notes
Validated the three risky changes against the 1.22.0 bytecode rather than the changelog:
initialize(ctx, domain)andisDomainScoped()are default methods, and the 2-arg default delegates to the 1-arg one.DevCycleProviderkeeps receiving the same call, so the readiness poll is unaffected.OpenFeatureAPI.shutdown(), not the provider contract. Worth knowing as a consumer-facing behavior change: anyone callingOpenFeatureAPI.shutdown()and then re-registering a provider must re-add global hooks and re-set the global evaluation context. Nothing in this repo does that.getLongEvaluationis a default that routes throughgetDoubleEvaluationwith range validation, which suits our all-doubles internal representation. Empty-string targeting keys were already guarded inDevCycleUser.java:147.Follow-up worth its own PR: the provider implements plain
FeatureProviderand never emitsPROVIDER_READY/PROVIDER_ERROR, which is whyinitialize()still needs the 2s busy-wait poll.