[openfeaturebot]

🤖 I have created a release beep boop

2.0.0 (2026-11-06)

⚠ BREAKING CHANGES

• bucket on any context type; (fractional re-assignment) (#1831)
• graceful fallback to code default when no default variant resolved (#1707)

🐛 Bug Fixes

• flagd-api-testkit: fix release-please version (#1751) (8f6b6c2)
• flagd: fix wrong environment variable and test execution (#1589) (e1d8e54)
• go-feature-flag: Fix javadoc generation blocking release please (#1592) (7a3a8f4)
• keep distributionManagement in flattened pom (#1807) (b20829c)
• README, and update publish plugin (16bd172)
• remove SBOM from maven bundle, README typo (5eecf75)
• security: update dependency org.assertj:assertj-core to v3.27.7 [security] (#1690) (257083e)
• testkit dep hierarchy (df3aa5b)
• various custom operator conformance fixes (#1778) (cced215)

✨ New Features

• 1.0 flagd core transitive deps (#1755) (fec3753)
• 1.0 flagd core transitive deps (#1758) (f81f2a9)
• add flagd-api-testkit module (#1742) (20e7181)
• add GCP Secret Manager OpenFeature provider (#1772) (17de2b7)
• Add Optimizely provider (#1510) (482daea)
• bucket on any context type; (fractional re-assignment) (#1831) (a6cc606)
• codereadiness: add hook for version-based flag validation (#1819) (d5c193a)
• compile go-feature-flag to Java bytecode (#1628) (129c9bd)
• extract core flagd evaluation and API modules (#1696) (fe98d88)
• gcp: add parameter manager support (#1808) (f3df150)
• graceful fallback to code default when no default variant resolved (#1707) (71fd7d0)
• json-logic++ (precompilation), improve e2e (#1968) (ad4ad04)
• lossless numeric coercion and safe range (#1959) (d69a23f)
• ofrep provider (#1429) (a33ef58)
• provider-tck: add Java conformance suite for OpenFeature providers (#1830) (8ce017d)

---

This PR was generated with Release Please. See documentation.

[toddbaert]

Blocking for now - there's no actual new features here for external users.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

• Last reviewed commit: e12bdf1
• Latest commit, not reviewed: 2ce0881

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review.

Walkthrough

Project version references change from 1.0.0 to 2.0.0 in three files. CHANGELOG.md adds the 2.0.0 release entry dated 2026-09-28, with a breaking change, bug fixes, and features.

Changes: Version Bump to 2.0.0

Layer / File(s)	Summary
Version identifiers and changelog .release-please-manifest.json, pom.xml, version.txt, CHANGELOG.md	The project version changes from 1.0.0 to 2.0.0. The changelog adds the 2.0.0 release entry with a breaking change, bug fixes, and features.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Suggested reviewers: toddbaert

Merge Risk: Minimal · up to e12bd

No actionable release risk is established; this change is mergeable after normal checks.

Pre-merge checks: 4

Check name	Status	Explanation
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Title check		The title clearly identifies this as a release of dev.openfeature.contrib.parent version 2.0.0, which matches the main changes.
Description check		The description covers the 2.0.0 release and related changes. Its release date is November 6, 2026; the changelog date is September 28, 2026.

Finishing Touches

Fix failing CI checks

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 70756d19-9b2d-4b8d-9ccd-bec158c7955c

📥 Commits

Reviewing files that changed from the base of the PR and between d0fc978 and e12bdf1.

📒 Files selected for processing (1)

• CHANGELOG.md

🚧 Files skipped from review as they are similar to previous changes (1)

• CHANGELOG.md

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

version.txt (1)

1-2: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Remove the stray second line from version.txt.

version.txt should contain a single version token; the extra 2 on Line 2 can break parsers expecting exact semver content.

Proposed fix

 2.0.0
-2

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@version.txt` around lines 1 - 2, Remove the extra trailing token from
version.txt so it contains only the single version value. Update the file
contents to keep just the 2.0.0 version string and delete the stray second line
entry, since version.txt should be a one-token semver source.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@CHANGELOG.md`:
- Around line 23-24: The 2.0.0 release notes contain two identical feature
bullets, so update the changelog entries to remove the ambiguity by either
merging them into a single bullet or rewriting one of the items to clearly
distinguish its issue/commit context; make the change in the duplicate “1.0
flagd core transitive deps” entries so the release notes read cleanly and
uniquely.

---

Outside diff comments:
In `@version.txt`:
- Around line 1-2: Remove the extra trailing token from version.txt so it
contains only the single version value. Update the file contents to keep just
the 2.0.0 version string and delete the stray second line entry, since
version.txt should be a one-token semver source.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: bcbe592d-bdd6-4f15-b070-3ccf66ae1422

📥 Commits

Reviewing files that changed from the base of the PR and between 72c275c and 1335f71.

📒 Files selected for processing (4)

• .release-please-manifest.json
• CHANGELOG.md
• pom.xml
• version.txt

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Clarify duplicate feature bullets in the 2.0.0 notes.

Lines 23–24 repeat the same feature text, which is confusing in user-facing release notes; please disambiguate or merge them.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CHANGELOG.md` around lines 23 - 24, The 2.0.0 release notes contain two
identical feature bullets, so update the changelog entries to remove the
ambiguity by either merging them into a single bullet or rewriting one of the
items to clearly distinguish its issue/commit context; make the change in the
duplicate “1.0 flagd core transitive deps” entries so the release notes read
cleanly and uniquely.