chore: update sdk readmes

Signed-off-by: OpenFeature Bot <[email protected]>

Author: openfeaturebot

docs/reference/technologies/client/kotlin.mdx

@@ -10,16 +10,16 @@ This content has been automatically generated from kotlin-sdk.
 Edits should be made here: https://github.com/open-feature/kotlin-sdk
 Once a repo has been updated, docs can be generated by running: yarn update:sdk-docs
 
-Last updated at Mon Sep 08 2025 11:54:08 GMT-0400 (Eastern Daylight Time)
+Last updated at Mon Oct 06 2025 08:10:45 GMT+0000 (Coordinated Universal Time)
 -->
 
 <p align="center" class="github-badges">
   <a href="https://github.com/open-feature/spec/releases/tag/v0.8.0">
     <img alt="Specification" src="https://img.shields.io/static/v1?label=specification&message=v0.8.0&color=yellow&style=for-the-badge" />
   </a>
 
-  <a href="https://github.com/open-feature/kotlin-sdk/releases/tag/v0.6.2">
-    <img alt="Release" src="https://img.shields.io/static/v1?label=release&message=v0.6.2&color=blue&style=for-the-badge" />
+  <a href="https://github.com/open-feature/kotlin-sdk/releases/tag/v0.7.0">
+    <img alt="Release" src="https://img.shields.io/static/v1?label=release&message=v0.7.0&color=blue&style=for-the-badge" />
   </a>
 
   <br/>
@@ -62,7 +62,7 @@ Installation is preferred via Maven Central.
 
 ```kotlin
 dependencies {
-    api("dev.openfeature:kotlin-sdk:0.6.2")
+    api("dev.openfeature:kotlin-sdk:0.7.0")
 }
 ```
 
@@ -72,7 +72,7 @@ dependencies {
 kotlin {
     sourceSets {
         commonMain.dependencies {
-            api("dev.openfeature:kotlin-sdk:0.6.2")
+            api("dev.openfeature:kotlin-sdk:0.7.0")
         }
     }
 }

docs/reference/technologies/client/swift.mdx

@@ -10,7 +10,7 @@ This content has been automatically generated from swift-sdk.
 Edits should be made here: https://github.com/open-feature/swift-sdk
 Once a repo has been updated, docs can be generated by running: yarn update:sdk-docs
 
-Last updated at Mon Sep 08 2025 11:54:08 GMT-0400 (Eastern Daylight Time)
+Last updated at Mon Oct 06 2025 08:10:45 GMT+0000 (Coordinated Universal Time)
 -->
 
 <p align="center" class="github-badges">
@@ -109,7 +109,7 @@ Task {
 | ✅      | [Hooks](#hooks)                 | Add functionality to various stages of the flag evaluation life-cycle.                                                             |
 | ❌      | [Tracking](#tracking)           | Associate user actions with feature flag evaluations.                                                                              |
 | ❌      | [Logging](#logging)             | Integrate with popular logging packages.                                                                                           |
-| ❌      | [Named clients](#named-clients) | Utilize multiple providers in a single application.                                                                                |
+| ✅      | [MultiProvider](#multiprovider) | Utilize multiple providers in a single application.                                                                                |
 | ✅      | [Eventing](#eventing)           | React to state changes in the provider or flag management system.                                                                  |
 | ❌      | [Shutdown](#shutdown)           | Gracefully clean up a provider during application shutdown.                                                                        |
 | ✅      | [Extending](#extending)         | Extend OpenFeature with custom providers and hooks.                                                                                |
@@ -178,6 +178,89 @@ Logging customization is not yet available in the iOS SDK.
 
 Support for named clients is not yet available in the iOS SDK.
 
+### MultiProvider
+
+The `MultiProvider` allows you to combine multiple feature flag providers into a single provider, enabling you to use different providers for different flags or implement fallback mechanisms. This is useful when migrating between providers, implementing A/B testing across providers, or ensuring high availability.
+
+#### Basic Usage
+
+```swift
+import OpenFeature
+
+Task {
+    // Create individual providers
+    let primaryProvider = PrimaryProvider()
+    let fallbackProvider = FallbackProvider()
+    
+    // Create a MultiProvider with default FirstMatchStrategy
+    let multiProvider = MultiProvider(providers: [primaryProvider, fallbackProvider])
+    
+    // Set the MultiProvider as the global provider
+    await OpenFeatureAPI.shared.setProviderAndWait(provider: multiProvider)
+    
+    // Use flags normally - the MultiProvider will handle provider selection
+    let client = OpenFeatureAPI.shared.getClient()
+    let flagValue = client.getBooleanValue(key: "my-flag", defaultValue: false)
+}
+```
+
+#### Evaluation Strategies
+
+The `MultiProvider` supports different strategies for evaluating flags across multiple providers:
+
+##### FirstMatchStrategy (Default)
+
+The `FirstMatchStrategy` evaluates providers in order and returns the first result that doesn't indicate "flag not found". If a provider returns an error other than "flag not found", that error is returned immediately.
+
+```swift
+let multiProvider = MultiProvider(
+    providers: [primaryProvider, fallbackProvider],
+    strategy: FirstMatchStrategy()
+)
+```
+
+##### FirstSuccessfulStrategy
+
+The `FirstSuccessfulStrategy` evaluates providers in order and returns the first successful result (no error). Unlike `FirstMatchStrategy`, it continues to the next provider if any error occurs, including "flag not found".
+
+```swift
+let multiProvider = MultiProvider(
+    providers: [primaryProvider, fallbackProvider],
+    strategy: FirstSuccessfulStrategy()
+)
+```
+
+#### Use Cases
+
+**Provider Migration:**
+```swift
+// Gradually migrate from OldProvider to NewProvider
+let multiProvider = MultiProvider(providers: [
+    NewProvider(),  // Check new provider first
+    OldProvider()   // Fall back to old provider
+])
+```
+
+**High Availability:**
+```swift
+// Use multiple providers for redundancy
+let multiProvider = MultiProvider(providers: [
+    RemoteProvider(),
+    LocalCacheProvider(),
+    StaticProvider()
+])
+```
+
+**Environment-Specific Providers:**
+```swift
+// Different providers for different environments
+let providers = [
+    EnvironmentProvider(environment: "production"),
+    DefaultProvider()
+]
+let multiProvider = MultiProvider(providers: providers)
+```
+
 ### Eventing
 
 Events allow you to react to state changes in the provider or underlying flag management system, such as flag definition changes, provider readiness, or error conditions.

docs/reference/technologies/client/web/angular.mdx

@@ -10,16 +10,16 @@ This content has been automatically generated from js-sdk.
 Edits should be made here: https://github.com/open-feature/js-sdk
 Once a repo has been updated, docs can be generated by running: yarn update:sdk-docs
 
-Last updated at Mon Sep 08 2025 11:54:09 GMT-0400 (Eastern Daylight Time)
+Last updated at Mon Oct 06 2025 08:10:45 GMT+0000 (Coordinated Universal Time)
 -->
 
 <p align="center" class="github-badges">
   <a href="https://github.com/open-feature/spec/releases/tag/v0.8.0">
     <img alt="Specification" src="https://img.shields.io/static/v1?label=specification&message=v0.8.0&color=yellow&style=for-the-badge" />
   </a>
 
-  <a href="https://github.com/open-feature/js-sdk/releases/tag/angular-sdk-v0.0.16">
-    <img alt="Release" src="https://img.shields.io/static/v1?label=release&message=v0.0.16&color=blue&style=for-the-badge" />
+  <a href="https://github.com/open-feature/js-sdk/releases/tag/angular-sdk-v0.0.17">
+    <img alt="Release" src="https://img.shields.io/static/v1?label=release&message=v0.0.17&color=blue&style=for-the-badge" />
   </a>
 
   <br/>
@@ -140,6 +140,13 @@ No `else`, `initializing`, or `reconciling` templates are required in this case.
 
 #### How to use
 
+The library provides two main ways to work with feature flags:
+
+1. **Structural Directives** - For template-based conditional rendering
+2. **FeatureFlagService** - For programmatic access with Observables
+
+##### Structural Directives
+
 The library provides four primary directives for feature flags, `booleanFeatureFlag`,
 `numberFeatureFlag`, `stringFeatureFlag` and `objectFeatureFlag`.
 
@@ -163,7 +170,7 @@ The template referenced in `initializing` and `reconciling` will be rendered if
 corresponding states.
 This parameter is _optional_, if omitted, the `then` and `else` templates will be rendered according to the flag value.
 
-##### Boolean Feature Flag
+###### Boolean Feature Flag
 
 ```html
 <div
@@ -181,7 +188,7 @@ This parameter is _optional_, if omitted, the `then` and `else` templates will b
 </ng-template>
 ```
 
-##### Number Feature Flag
+###### Number Feature Flag
 
 ```html
 <div
@@ -199,7 +206,7 @@ This parameter is _optional_, if omitted, the `then` and `else` templates will b
 </ng-template>
 ```
 
-##### String Feature Flag
+###### String Feature Flag
 
 ```html
 <div
@@ -217,7 +224,7 @@ This parameter is _optional_, if omitted, the `then` and `else` templates will b
 </ng-template>
 ```
 
-##### Object Feature Flag
+###### Object Feature Flag
 
 ```html
 <div
@@ -235,7 +242,7 @@ This parameter is _optional_, if omitted, the `then` and `else` templates will b
 </ng-template>
 ```
 
-##### Opting-out of automatic re-rendering
+###### Opting-out of automatic re-rendering
 
 By default, the directive re-renders when the flag value changes or the context changes.
 
@@ -247,7 +254,7 @@ In cases, this is not desired, re-rendering can be disabled for both events:
 </div>
 ```
 
-##### Consuming the evaluation details
+###### Consuming the evaluation details
 
 The `evaluation details` can be used when rendering the templates.
 The directives [`$implicit`](https://angular.dev/guide/directives/structural-directives#structural-directive-shorthand)
@@ -278,6 +285,86 @@ This can be used to just render the flag value or details without conditional re
 </div>
 ```
 
+##### FeatureFlagService
+
+The `FeatureFlagService` provides programmatic access to feature flags through reactive patterns. All methods return
+Observables that automatically emit new values when flag configurations or evaluation context changes.
+
+###### Using with Observables
+
+```typescript
+import { Component, inject } from '@angular/core';
+import { AsyncPipe } from '@angular/common';
+import { FeatureFlagService } from '@openfeature/angular-sdk';
+
+@Component({
+  selector: 'my-component',
+  standalone: true,
+  imports: [AsyncPipe],
+  template: `
+    <div *ngIf="(isFeatureEnabled$ | async)?.value">
+      Feature is enabled! Reason: {{ (isFeatureEnabled$ | async)?.reason }}
+    </div>
+    <div>Theme: {{ (currentTheme$ | async)?.value }}</div>
+    <div>Max items: {{ (maxItems$ | async)?.value }}</div>
+  `
+})
+export class MyComponent {
+  private flagService = inject(FeatureFlagService);
+
+  // Boolean flag
+  isFeatureEnabled$ = this.flagService.getBooleanDetails('my-feature', false);
+
+  // String flag
+  currentTheme$ = this.flagService.getStringDetails('theme', 'light');
+
+  // Number flag
+  maxItems$ = this.flagService.getNumberDetails('max-items', 10);
+
+  // Object flag with type safety
+  config$ = this.flagService.getObjectDetails<{ timeout: number }>('api-config', { timeout: 5000 });
+}
+```
+
+###### Using with Angular Signals
+
+You can convert any Observable from the service to an Angular Signal using `toSignal()`:
+
+```typescript
+import { Component, inject } from '@angular/core';
+import { toSignal } from '@angular/core/rxjs-interop';
+import { FeatureFlagService } from '@openfeature/angular-sdk';
+
+@Component({
+  selector: 'my-component',
+  standalone: true,
+  template: `
+    <div *ngIf="isFeatureEnabled()?.value">
+      Feature is enabled! Reason: {{ isFeatureEnabled()?.reason }}
+    </div>
+    <div>Theme: {{ currentTheme()?.value }}</div>
+  `
+})
+export class MyComponent {
+  private flagService = inject(FeatureFlagService);
+
+  // Convert Observables to Signals
+  isFeatureEnabled = toSignal(this.flagService.getBooleanDetails('my-feature', false));
+  currentTheme = toSignal(this.flagService.getStringDetails('theme', 'light'));
+}
+```
+
+###### Service Options
+
+The service methods accept the [same options as the directives](#opting-out-of-automatic-re-rendering):
+
+```typescript
+const flag$ = this.flagService.getBooleanDetails('my-flag', false, 'my-domain', {
+  updateOnConfigurationChanged: false,  // default: true
+  updateOnContextChanged: false,        // default: true
+});
+```
+
 ##### Setting evaluation context
 
 To set the initial evaluation context, you can add the `context` parameter to the `OpenFeatureModule` configuration.

docs/reference/technologies/client/web/index.mdx

@@ -10,16 +10,16 @@ This content has been automatically generated from js-sdk.
 Edits should be made here: https://github.com/open-feature/js-sdk
 Once a repo has been updated, docs can be generated by running: yarn update:sdk-docs
 
-Last updated at Mon Sep 08 2025 11:54:08 GMT-0400 (Eastern Daylight Time)
+Last updated at Mon Oct 06 2025 08:10:45 GMT+0000 (Coordinated Universal Time)
 -->
 
 <p align="center" class="github-badges">
   <a href="https://github.com/open-feature/spec/releases/tag/v0.8.0">
     <img alt="Specification" src="https://img.shields.io/static/v1?label=specification&message=v0.8.0&color=yellow&style=for-the-badge" />
   </a>
 
-  <a href="https://github.com/open-feature/js-sdk/releases/tag/web-sdk-v1.6.1">
-    <img alt="Release" src="https://img.shields.io/static/v1?label=release&message=v1.6.1&color=blue&style=for-the-badge" />
+  <a href="https://github.com/open-feature/js-sdk/releases/tag/web-sdk-v1.6.2">
+    <img alt="Release" src="https://img.shields.io/static/v1?label=release&message=v1.6.2&color=blue&style=for-the-badge" />
   </a>
 
   <br/>

docs/reference/technologies/client/web/react.mdx

@@ -10,7 +10,7 @@ This content has been automatically generated from js-sdk.
 Edits should be made here: https://github.com/open-feature/js-sdk
 Once a repo has been updated, docs can be generated by running: yarn update:sdk-docs
 
-Last updated at Mon Sep 08 2025 11:54:08 GMT-0400 (Eastern Daylight Time)
+Last updated at Mon Oct 06 2025 08:10:45 GMT+0000 (Coordinated Universal Time)
 -->
 
 <p align="center" class="github-badges">

docs/reference/technologies/server/dart.mdx

@@ -9,7 +9,7 @@ This content has been automatically generated from dart-server-sdk.
 Edits should be made here: https://github.com/open-feature/dart-server-sdk
 Once a repo has been updated, docs can be generated by running: yarn update:sdk-docs
 
-Last updated at Mon Sep 08 2025 11:54:09 GMT-0400 (Eastern Daylight Time)
+Last updated at Mon Oct 06 2025 08:10:45 GMT+0000 (Coordinated Universal Time)
 -->
 
 <p align="center" class="github-badges">
@@ -19,8 +19,8 @@ Last updated at Mon Sep 08 2025 11:54:09 GMT-0400 (Eastern Daylight Time)
   </a>
 
 
-  <a href="https://github.com/open-feature/dart-server-sdk/releases/tag/v0.0.12">
-    <img alt="Release" src="https://img.shields.io/static/v1?label=release&message=v0.0.12&color=blue&style=for-the-badge" />
+  <a href="https://github.com/open-feature/dart-server-sdk/releases/tag/v0.0.13">
+    <img alt="Release" src="https://img.shields.io/static/v1?label=release&message=v0.0.13&color=blue&style=for-the-badge" />
   </a>
 
   <a href="https://dart.dev/">
@@ -56,7 +56,7 @@ Dart language version: [3.9.2](https://dart.dev/get-dart/archive)
 
 ```yaml
 dependencies:
-  openfeature_dart_server_sdk: ^0.0.12
+  openfeature_dart_server_sdk: ^0.0.13
 ```
 
 ### Then run:

docs/reference/technologies/server/dotnet.mdx

@@ -10,7 +10,7 @@ This content has been automatically generated from dotnet-sdk.
 Edits should be made here: https://github.com/open-feature/dotnet-sdk
 Once a repo has been updated, docs can be generated by running: yarn update:sdk-docs
 
-Last updated at Mon Sep 08 2025 11:54:07 GMT-0400 (Eastern Daylight Time)
+Last updated at Mon Oct 06 2025 08:10:45 GMT+0000 (Coordinated Universal Time)
 -->
 
 [![Specification](https://img.shields.io/static/v1?label=specification&message=v0.8.0&color=yellow&style=for-the-badge)](https://github.com/open-feature/spec/releases/tag/v0.8.0)