Skip to content

chore(docs): clarify some breaking changes in v10 - #368

Merged
gastonfournier merged 4 commits into
mainfrom
2-4154
Feb 9, 2026
Merged

chore(docs): clarify some breaking changes in v10#368
gastonfournier merged 4 commits into
mainfrom
2-4154

Conversation

@gastonfournier

Copy link
Copy Markdown
Contributor

Clarify breaking changes and add details to the migration guide.

Closes #367

Copilot AI review requested due to automatic review settings February 9, 2026 09:30
@gastonfournier gastonfournier self-assigned this Feb 9, 2026
@coveralls

This comment was marked as outdated.

This comment was marked as outdated.

@sighphyre sighphyre left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LG, thank you!

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread v10_MIGRATION_GUIDE.md
`GradualRolloutRandomStrategy`, `GradualRolloutUserWithIdStrategy`, and
`GradualRolloutSessionIdStrategy`) are no longer part of the Java SDK public API in v10.

These strategies are evaluated internally by Yggdrasil. There is no class-for-class replacement to import for built-ins; use the built-ins via Unleash configuration, and implement `Strategy` only for custom or fallback behavior.

Copilot AI Feb 9, 2026

Copy link

Choose a reason for hiding this comment

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

“use the built-ins via Unleash configuration” is ambiguous in this repo because “configuration” often refers to UnleashConfig (SDK-side). Consider clarifying that built-in strategies are selected/configured on the Unleash server/UI (i.e., by strategy name in feature flag definitions), not by importing Java classes.

Suggested change
These strategies are evaluated internally by Yggdrasil. There is no class-for-class replacement to import for built-ins; use the built-ins via Unleash configuration, and implement `Strategy` only for custom or fallback behavior.
These strategies are evaluated internally by Yggdrasil. There is no class-for-class replacement to import for built-ins in the Java SDK; to use these built-ins, select the corresponding built-in strategy names when configuring your feature flags in the Unleash server/UI, and implement `Strategy` only for custom or fallback behavior in your own code.

Copilot uses AI. Check for mistakes.
@github-project-automation github-project-automation Bot moved this from New to Approved PRs in Issues and PRs Feb 9, 2026
@gastonfournier
gastonfournier merged commit e3b1bf6 into main Feb 9, 2026
9 checks passed
@gastonfournier
gastonfournier deleted the 2-4154 branch February 9, 2026 09:57
@github-project-automation github-project-automation Bot moved this from Approved PRs to Done in Issues and PRs Feb 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Lack of replacement for strategies removed in version 10

5 participants