Repository navigation
Releases: open-feature/dart-sdk
Release list
v0.1.0
0.1.0 (2026-10-05)
Regular, non-beta server 0.1.0 milestone. The package remains pre-1.0 and does
not claim complete OpenFeature v0.9 conformance.
Compatibility: Dart pub constraints such as ^0.0.26 and ^0.0.27 exclude
0.1.0. Applications and providers must review their SDK constraints before
upgrading; an IntelliToggle provider update is required to admit this version.
🐛 Bug Fixes
v0.0.27
openfeature_dart_client_sdk: v0.0.1
0.0.1 (2026-10-05)
First non-beta client release. The package remains pre-1.0; this version does
not establish a 1.0 API compatibility commitment. The three-second deadline
below belongs to the development-only provider contract, not the application
lifecycle timeout.
🐛 Bug Fixes
openfeature_dart_client_sdk: v0.0.1-beta.2
v0.0.26
0.0.26 (2026-09-24)
Breaking source change: server tracking value
TrackingEventDetails.value changes from double? to num?, preserving integer tracking values. Consumers assigning this property to double? must use details.value?.toDouble() or accept num?. Existing double constructor arguments and nullable values remain supported. This change first ships in server 0.0.26; it is not part of published 0.0.25. The client package remains a separate beta release.
This migration notice supplements the published release notes. The already-published package archive and version tag are unchanged.
🧹 Chore
v0.0.25
v0.0.24
0.0.24 (2026-08-28)
This release repackages the server SDK under packages/openfeature_dart_server_sdk. The Dart package name, pub.dev dependency, public API, and package: imports are unchanged.
Repository layout migration
- Move the published server package from the repository root to
packages/openfeature_dart_server_sdk(#151). - Git dependencies must now set
path: packages/openfeature_dart_server_sdk; pub.dev consumers require no dependency or import changes.
openfeature_dart_client_sdk: v0.0.1-beta.1
v0.0.23
0.0.23 (2026-08-14)
This release contains the first lifecycle and evaluation-safety work toward
OpenFeature v0.9.0. It does not claim complete v0.9 conformance; remaining
requirements are tracked in
#121.
Notable compatibility changes
- Raise the minimum supported Dart SDK from 3.11.4 to 3.12.2
(#123). - Make
OpenFeatureAPI.resetInstance()asynchronous so callers can await
provider and controller teardown before creating a replacement API instance
(#138). - Make
FlagEvaluationDetails.flagMetadatanon-nullable and immutable. Missing
metadata now defaults to an empty map, and mutation attempts throw
UnsupportedError
(#126,
#132).
Features
- Add provider-owned lifecycle events and per-instance lifecycle coordination,
including dynamic client rebinding, domain-scoped providers, final-binding
shutdown, and explicit wait-for-readiness APIs
(#124).
Bug fixes
- Contain provider, hook, and context-resolution failures while preserving
targeting keys and caller defaults
(#126). - Preserve the latest concurrent provider and domain binding request, serialize
rebinding with provider shutdown, and prevent late initialization from
restoring stale bindings
(#132,
#133,
#134,
#138).
Documentation
- Add the server v0.9 conformance matrix and provider-lifecycle compatibility
contract
(#122). - Add the proposed pure-Dart client SDK architecture and conformance matrix;
the client SDK is not implemented or published in this release
(#118,
#136). - Clarify the public README's asynchronous lifecycle examples and client SDK
proposal status
(#143,
#144).
CI and release maintenance
- Publish each version once and harden release, validation, coverage, branch,
formatting, and minimum-dependency workflows
(#119,
#125,
#127,
#128,
#130). - Use the conventional
doc/package layout and add DCO remediation support
for shared-branch squash commits
(#129,
#135).
Final QA
- Dart formatting: clean (34 files, 0 changed)
- Static analysis: no issues
- Tests: 181 passed
- Package publish dry run: 0 warnings