chore: release main

[github-actions]

🤖 I have created a release beep boop

launchdarkly-cpp-client: 3.11.2

3.11.2 (2026-06-04)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @launchdarkly/cpp-sse-client bumped from 0.6.1 to 0.7.0

launchdarkly-cpp-server: 3.11.0

3.11.0 (2026-06-04)

Features

• add IBigSegmentStore interface + Redis and DynamoDB stores (#536) (136aca7)
• add internal BigSegmentsBuilder + config struct (#541) (3c88c2a)
• add server FDv2 data system orchestrator (#529) (65e110f)
• add X-LaunchDarkly-Instance-Id header to server SDK (SDK-2353) (#532) (fd0c761)
• propagate FDv1 fallback directive from FDv2 polling and streaming sources (#538) (edd96fe)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @launchdarkly/cpp-sse-client bumped from 0.6.1 to 0.7.0

launchdarkly-cpp-server-dynamodb-source: 0.2.0

0.2.0 (2026-06-04)

Features

• add IBigSegmentStore interface + Redis and DynamoDB stores (#536) (136aca7)
• implement DynamoDBDataSource + tests (#534) (a0c2790)
• scaffold libs/server-sdk-dynamodb-source (#533) (df386c1)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @launchdarkly/cpp-server bumped from 3.10.1 to 3.11.0

launchdarkly-cpp-server-otel: 0.1.2

0.1.2 (2026-06-04)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @launchdarkly/cpp-server bumped from 3.10.1 to 3.11.0

launchdarkly-cpp-server-redis-source: 2.3.0

2.3.0 (2026-06-04)

Features

• add IBigSegmentStore interface + Redis and DynamoDB stores (#536) (136aca7)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @launchdarkly/cpp-server bumped from 3.10.1 to 3.11.0

launchdarkly-cpp-sse-client: 0.7.0

0.7.0 (2026-06-04)

Features

• propagate FDv1 fallback directive from FDv2 polling and streaming sources (#538) (edd96fe)

---

This PR was generated with Release Please. See documentation.

---

Note

Low Risk
Mechanical release metadata only; no runtime or API logic changes in the diff.

Overview
Release Please version bump across the C++ SDK workspace: updates .release-please-manifest.json, per-package CHANGELOG.md entries, CMakeLists.txt VERSION, embedded kVersion / Version() strings, package.json dependency pins, and version assertions in client/server tests.

Published versions: client 3.11.2 (SSE client 0.7.0 only); server 3.11.0; SSE 0.7.0; Redis source 2.3.0; DynamoDB source 0.2.0; server OTel 0.1.2. Changelog text for server 3.11.0 and related packages records already-merged work (FDv2 orchestration, big-segment stores, instance ID header, FDv1 fallback propagation)—this PR does not introduce that behavior, it tags releases.

^{Reviewed by Cursor Bugbot for commit 3a078b5. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default mode and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 505b538. Configure here.}

[cursor]

Otel CMakeLists.txt version not updated to 0.1.2

Medium Severity

The libs/server-sdk-otel/CMakeLists.txt reports VERSION 0.1.0 but this release publishes version 0.1.2. Unlike all sibling packages, this file is missing the # {x-release-please-version} marker comment, so Release Please cannot find and update the version string — even though the file is explicitly listed in release-please-config.json under extra-files. This leaves the CMake project version permanently stale relative to the released version.

 

^{Reviewed by Cursor Bugbot for commit 505b538. Configure here.}