Skip to content

chore: release main#530

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main
Open

chore: release main#530
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented May 6, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

launchdarkly-cpp-client: 3.11.2

3.11.2 (2026-06-11)

Dependencies

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

0.14.0 (2026-06-11)

Features

  • add internal BigSegmentStoreWrapper with caching and status polling (#543) (47fa5c2)
  • orchestrator switches to FDv1 fallback on directive (#539) (44f2522)

Bug Fixes

  • FDv2 fixes surfaced by v3 contract test harness (#547) (e9c3c04)
launchdarkly-cpp-server: 3.11.0

3.11.0 (2026-06-11)

Features

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

Bug Fixes

  • FDv2 fixes surfaced by v3 contract test harness (#547) (e9c3c04)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @launchdarkly/cpp-internal bumped from 0.13.0 to 0.14.0
      • @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-11)

Features

  • add IBigSegmentStore interface + Redis and DynamoDB stores (#536) (136aca7)
  • add internal BigSegmentStoreWrapper with caching and status polling (#543) (47fa5c2)
  • 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-11)

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-11)

Features

  • add IBigSegmentStore interface + Redis and DynamoDB stores (#536) (136aca7)
  • add internal BigSegmentStoreWrapper with caching and status polling (#543) (47fa5c2)

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-11)

Features

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

This PR was generated with Release Please. See documentation.


Note

Medium Risk
The tagged libraries include changes to flag delivery orchestration, big-segment evaluation, and FDv2 behavior; this PR is metadata-only but consumers pick up those behavioral releases.

Overview
Release Please cut for the C++ SDK monorepo: bumps .release-please-manifest.json, per-package CHANGELOG.md, package.json workspace deps, CMake VERSION, public Version() strings, and version assertions in tests—no new runtime logic in this diff.

Server 3.11.0 (and aligned internal 0.14.0, SSE 0.7.0, Redis 2.3.0, DynamoDB source 0.2.0, OTEL 0.1.2) documents FDv2 data-system orchestration with FDv1 fallback from streaming/polling, big-segment store plumbing (IBigSegmentStore, wrapper with cache/polling), X-LaunchDarkly-Instance-Id, and FDv2 contract-test fixes. Client 3.11.2 is a patch release that only refreshes dependencies on those bumped libs.

Reviewed by Cursor Bugbot for commit 0774918. Bugbot is set up for automated code reviews on this repo. Configure here.

@github-actions github-actions Bot requested a review from a team as a code owner May 6, 2026 22:54
@github-actions github-actions Bot force-pushed the release-please--branches--main branch from f20e0b3 to b5f8572 Compare May 7, 2026 17:26
@github-actions github-actions Bot force-pushed the release-please--branches--main branch from b5f8572 to 505b538 Compare May 14, 2026 17:37

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Fix All in Cursor

❌ 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.

"name": "@launchdarkly/cpp-server-otel",
"description": "This package.json exists for modeling dependencies for the release process.",
"version": "0.1.1",
"version": "0.1.2",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 505b538. Configure here.

@github-actions github-actions Bot force-pushed the release-please--branches--main branch 3 times, most recently from 1636b9e to 6c17ed0 Compare May 18, 2026 05:56
@github-actions github-actions Bot force-pushed the release-please--branches--main branch 7 times, most recently from 23d6b5d to 3a078b5 Compare June 4, 2026 00:04
@github-actions github-actions Bot force-pushed the release-please--branches--main branch 4 times, most recently from 33d01d6 to db0c337 Compare June 11, 2026 17:58
@github-actions github-actions Bot force-pushed the release-please--branches--main branch from db0c337 to 0774918 Compare June 11, 2026 21:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants