[github-actions]

🤖 I have created a release beep boop

0.6.0-alpha (2026-11-05)

⚠ BREAKING CHANGES

• update flagd-core to the latest major (#46)

✨ New Features

• base provider state on CDN fetches only, not SSE connection state (#44) (dd3b485)
• sse test case implementation (ref: AI-724) (#36) (50bf529)
• update flagd-core to the latest major (#46) (f99f37d)

🐛 Bug Fixes

• bound fetch duration and enforce single-flight CDN fetches (#37) (ef0673d)
• deps: bump jackson-databind to 2.22.4 (ref: ICP-11215) (#48) (671da25)
• use a 150s read timeout for the SSE connection (#45) (b5fc05d)

🧹 Chore

• deps: bump com.fasterxml.jackson.core:jackson-databind from 2.22.1 to 2.22.3 (#41) (1c2a1a6)
• deps: bump local-demo provider pin to 0.5.0-alpha (#32) (abf97a5)
• update the metrics url for LocalDemo.java NOISSUE (#34) (b340003)

📚 Documentation

• align README with the standard provider format (#35) (2c74f36)

🔄 Refactoring

• rename triggerSseRefetch to requestOutOfBandFetch (#43) (29b5519)

---

This PR was generated with Release Please. See documentation.

[Copilot]

🟡 Changes recommended

The breaking-change notice omits that fractional bucket assignment changes can give existing targeting keys different variants after upgrading, even with unchanged flag configuration.

1 open issue

• Add rollout impact to breaking-change notice · New

What changed in this PR

Prepares the Dynatrace OpenFeature Java provider’s 0.6.0-alpha release by updating version references and documenting changes since 0.5.0-alpha.

Changes:

• Aligns the Maven artifact version, release metadata, and installation examples with 0.6.0-alpha.
• Adds release notes covering the breaking flagd-core upgrade, CDN fetch fixes, and other previously merged updates.

File	Description
version.txt	Sets the release version to 0.6.0-alpha.
README.md	Updates Maven and Gradle installation examples.
pom.xml	Updates the provider artifact version.
CHANGELOG.md	Adds the 0.6.0-alpha release notes.
.release-please-manifest.json	Updates the version tracked by Release Please.

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

The changelog omits that the dependency upgrade changes fractional bucket assignments, potentially assigning different rollout variants to existing targeting keys.

1 open issue

• Add rollout impact to breaking-change notice

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

The breaking-change notice omits that fractional bucket assignments change after the dependency upgrade, potentially giving existing targeting keys different variants even when rollout configurations are unchanged.

1 open issue

• Add rollout impact to breaking-change notice

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

The release note omits the breaking change that existing targeting keys may receive different variants after upgrading, even with unchanged flag configuration.

1 open issue

• Add rollout impact to breaking-change notice

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

The changelog omits that existing fractional rollouts can assign different variants after upgrading, leaving users unable to assess rollout continuity.

1 open issue

• Add rollout impact to breaking-change notice

_{Review effort: Balanced}