chore(main): release dev.openfeature.contrib.parent 2.0.0

[openfeaturebot]

🤖 I have created a release beep boop

2.0.0 (2026-06-24)

⚠ BREAKING CHANGES

• 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)
• 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)
• 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)
• ofrep provider (#1429) (a33ef58)

---

This PR was generated with Release Please. See documentation.

[toddbaert]

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

[coderabbitai]

📝 Walkthrough

Walkthrough

Four files are updated to bump the project version from 1.0.0 to 2.0.0: .release-please-manifest.json, pom.xml, and version.txt each have their version string changed, while CHANGELOG.md receives a new 2.0.0 section dated 2026-06-24 with breaking changes, bug fixes, and new features entries.

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	Root version updated from 1.0.0 to 2.0.0 in all version-tracking files; CHANGELOG.md gains the 2.0.0 release section documenting breaking changes (graceful fallback when no default variant is resolved), bug fixes, and new features.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies this as a 2.0.0 release for dev.openfeature.contrib.parent.
Description check	✅ Passed	The description matches the release changes and notes for version 2.0.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands.}

[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.