Skip to content

Prepare Java server SDK 6.0.0 with stable common v4 - #158

Merged
typotter merged 6 commits into
mainfrom
typo/release-v6
Oct 30, 2026
Merged

typotter merged 6 commits into
mainfrom
typo/release-v6

Conversation

@typotter

@typotter typotter commented Oct 5, 2026 •

Copy link
Copy Markdown
Collaborator

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

  • Replace snapshot dependencies with common 4.0.3 and align the framework tests classifier with the runtime framework version.
  • Expose assignment-details APIs, preserve concrete JSON/configuration method descriptors used by existing callers, and allow applications to supply an EppoConfigurationClient through the builder.
  • Document the DTO and configuration-builder migrations, removed APIs, strict/graceful JSON behaviour, HTTP 304 callbacks, and bandit failure/recovery semantics.
  • Remove unused direct Ehcache and java-semver dependencies. Preserve the dependency-security updates already merged into main.

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?

  • Java 8/11/17/21: 73 tests per runtime, zero failures/errors/skips; formatting, release-version guard and migration probes passed.
  • Full local scenario API, relay and shared runner: 256 passed, zero failures/errors, two expected unsupported dynamic-typing skips.
  • An unchanged caller compiled against server 5.3.4 links on all four runtimes.
  • Runtime and tests resolve common 4.0.3/framework 0.1.3. Relay core JAR hashes match Maven Central downloads; Maven Local and snapshot repositories were excluded.
  • Signed commit and diff whitespace verification passed.
  • Fresh remote CI passed all four Java jobs.
  • Hosted-environment validation is not claimed. After release, verify the published server artifact resolves from Maven Central.

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.
Comment thread README.md Resolved
Comment thread build.gradle Resolved
Comment thread build.gradle Resolved
Comment thread build.gradle Resolved
Comment thread build.gradle Resolved
Comment thread build.gradle Resolved
Comment thread build.gradle Resolved
aarsilv and others added 4 commits October 28, 2026 20:57
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>
@typotter
typotter requested a review from aarsilv October 30, 2026 18:32

@aarsilv aarsilv left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for iterating! 🚀

@typotter
typotter merged commit 9175b7e into main Oct 30, 2026
6 checks passed
@typotter
typotter deleted the typo/release-v6 branch October 30, 2026 19:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants