chore(main): release openfeature-provider-flagd 0.6.0

[openfeaturebot]

🤖 I have created a release beep boop

0.6.0 (2026-10-15)

⚠ BREAKING CHANGES

• bucket on any context type; (fractional re-assignment) (#415)

✨ New Features

• bucket on any context type; (fractional re-assignment) (#415) (e4681b0)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

Warning

Review limit reached

This review ran on the open-source allowance, not this organization's plan, because the pull request author doesn't have an assigned seat. Waiting won't change this — ask an organization admin to assign them a seat, or add seats in Billing if every seat is already assigned, then retry.

Next included review available in 9 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 08949f2a-a06f-4222-b792-106f766d09aa

📥 Commits

Reviewing files that changed from the base of the PR and between 2d0b0a3 and 9ae48d2.

📒 Files selected for processing: 3

• .release-please-manifest.json
• providers/openfeature-provider-flagd/CHANGELOG.md
• providers/openfeature-provider-flagd/pyproject.toml

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 2c6cad59-2618-47d5-9bb3-99619d61f8fc

📥 Commits

Reviewing files that changed from the base of the PR and between e4681b0 and 2d0b0a3.

📒 Files selected for processing: 3

• .release-please-manifest.json
• providers/openfeature-provider-flagd/CHANGELOG.md
• providers/openfeature-provider-flagd/pyproject.toml

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

📝 Walkthrough

The flagd provider version changes from 0.5.2 to 0.6.0 in the release manifest and project metadata. The changelog adds a 0.6.0 entry dated 2026-10-15, describing fractional reassignment bucketing on any context type as a breaking change and a new feature.

Changes: flagd Provider Release

Layer / File(s)	Summary
Version 0.6.0 release metadata .release-please-manifest.json, providers/openfeature-provider-flagd/pyproject.toml, providers/openfeature-provider-flagd/CHANGELOG.md	The manifest and project metadata set the provider version to 0.6.0. The changelog adds the 0.6.0 release entry and lists fractional reassignment bucketing on any context type as a breaking change and a new feature.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: ⚪ Minimal · up to 2d0b0

The 0.6.0 release metadata and changelog are consistent with the implementation. The frozen lockfile does not block publication, so no actionable merge risk remains.

### Architecture Summary

Architecture risk: 🔵 Low · up to 2d0b0

The change affects 1 system.

Changed systems: providers

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — providers (service) was modified; 2 changed files map to changed impact.

Before / after behavior

• observed — Modified behavior in providers/openfeature-provider-flagd/CHANGELOG.md: Adds the 0.6.0 release entry dated 2026-10-15, listing fractional reassignment bucketing on any context type under both breaking changes and new features.
• observed — Modified behavior in providers/openfeature-provider-flagd/pyproject.toml: The project version changes from 0.5.2 to 0.6.0.
• observed — Modified behavior in .release-please-manifest.json: Updated the manifest version for providers/openfeature-provider-flagd from 0.5.2 to 0.6.0.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title clearly identifies the 0.6.0 release of the openfeature-provider-flagd package. It matches the main change.
Description check		The description documents the 0.6.0 release, including the breaking change and new feature. It is directly related to the changeset.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.

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

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.34%. Comparing base (105fa36) to head (9ae48d2).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #458      +/-   ##
==========================================
+ Coverage   90.53%   95.34%   +4.81%     
==========================================
  Files          17       24       +7     
  Lines         486     1075     +589     
==========================================
+ Hits          440     1025     +585     
- Misses         46       50       +4     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[openfeaturebot]

🤖 Created releases:

• openfeature-provider-flagd/v0.6.0

🌻