Repository navigation
Prepare Java server SDK 6.0.0 with stable common v4 - #158
Merged
Merged
Conversation
typotter
force-pushed
the
typo/release-v6
branch
from
October 15, 2026 06:26
671f86e to
2782abf
Compare
5 tasks
Use released common 4.0.1 and framework 0.1.1 test fixtures. Document the v6 API migration and strict-mode malformed-JSON behaviour. Validate Java 8, 11, 17 and 21 with 68 tests per runtime and migration probes; full relay passes 256 cases with two expected skips against published artifacts.
typotter
force-pushed
the
typo/release-v6
branch
from
October 22, 2026 15:34
2782abf to
40b0ac5
Compare
typotter
marked this pull request as ready for review
October 22, 2026 17:39
This was referenced Oct 23, 2026
aarsilv
reviewed
Oct 23, 2026
aarsilv
reviewed
Oct 23, 2026
aarsilv
reviewed
Oct 23, 2026
aarsilv
reviewed
Oct 23, 2026
aarsilv
reviewed
Oct 23, 2026
aarsilv
reviewed
Oct 23, 2026
aarsilv
reviewed
Oct 24, 2026
Common 4.0.2 keeps flags updating when a bandit fetch fails and returns the default value when bandit evaluation fails. Update the dependency pins and the 6.0.0 upgrade notes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- List the removed common APIs and the DTO package moves, including ShardRange and EppoModule, with a JacksonConfigurationParser example. - Say that the details APIs are new in 6.0.0, and that an unchanged configuration (HTTP 304) no longer calls onConfigurationChange. - Qualify the 4.0.2 bandit-failure note: graceful mode returns the default, strict mode throws, and the assignment logger has already recorded the bandit variation. - Say that snapshots publish only while the version ends in -SNAPSHOT. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Cover common 4.0.2's bandit handling: a failed bandit fetch still applies the flags, bandit flags return the default with BANDIT_ERROR, and the next poll retries the bandits. The test fails against common 4.0.1. Also run the shared assignment cases through the details APIs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Common 4 takes the configuration client as a constructor dependency, but EppoClient always passed a new OkHttpEppoClient, so 6.0.0 offered no way to replace it. Add Builder.configurationClient, which defaults to OkHttpEppoClient, and document it in the upgrade notes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
aarsilv
approved these changes
Oct 30, 2026
aarsilv
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for iterating! 🚀
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.
Eppo Internal
Related: #156 and Eppo-exp/sdk-common-jdk#273
Motivation and Context
Prepare Java server SDK 6.0.0 using published common 4.0.3 and framework 0.1.3. The common API is exposed transitively; its moved DTOs and removed public APIs require a major server release.
Description
A bandit fetch failure allows flags to update and retries models on the next poll. A graceful bandit evaluation failure returns the supplied default with a null action; details report BANDIT_ERROR. The assignment logger can already have recorded the flag's bandit variation.
After merge, publish through the GitHub release workflow. Resume snapshot publication with a follow-up snapshot version bump.
How has this been documented?
README upgrade notes cover the dependency and API changes, custom HTTP clients, details methods, JSON behaviour, callbacks, bandit recovery and removed transitive dependencies.
How has this been tested?