Skip to content

chore(main): release LaunchDarkly.ServerSdk 8.18.0 - #401

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

github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--LaunchDarkly.ServerSdk

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

8.18.0 (2026-11-20)

Features

  • Let each data source decide whether FDv2 writes its data to a persistent store (#389) (fae3200)

Bug Fixes

  • Accept flag and segment data that has null in optional properties (#413) (75a658f)
  • Clear empty FDv2 selectors in the server SDK (#407) (c92f5b2)
  • Fall through to the next FDv2 initializer when a polling response has no events (#415) (d32bdca)
  • Make TestData ValueForAll return its value when targeting is off (#400) (c8fef92)
  • Prevent flags in a persistent store from becoming available to mobile keys (#418) (16d1c05)
  • Retry a file data load whose read fails, and make the retry tests and the FDv2 fallback test robust to timing (#395) (741b662)
  • Write a JSON tombstone for deleted items in the DynamoDB store (#409) (d93f42a)

This PR was generated with Release Please. See documentation.


Note

Overview
This PR releases LaunchDarkly.ServerSdk 8.18.0 via Release Please: it bumps the package version in the manifest, LaunchDarkly.ServerSdk.csproj, PROVENANCE.md, and adds the 8.18.0 changelog section (no application source changes in the diff itself).

8.18.0 ships one feature—per-data-source control over whether FDv2 writes to a persistent store—plus fixes for FDv2 (optional null flag/segment fields, empty selector clearing, initializer fallback when polling has no events), TestData when targeting is off, file data load retries, DynamoDB JSON tombstones on delete, and a fix that keeps persistent-store flags from being exposed to mobile SDK keys.

Reviewed by Cursor Bugbot for commit fac2b5a. 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 November 6, 2026 17:07
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--LaunchDarkly.ServerSdk branch 5 times, most recently from 7f4a1db to f672f56 Compare November 10, 2026 21:01
@github-actions github-actions Bot changed the title chore(main): release LaunchDarkly.ServerSdk 8.17.3 chore(main): release LaunchDarkly.ServerSdk 8.18.0 Nov 10, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--LaunchDarkly.ServerSdk branch 2 times, most recently from ab48fd1 to 2b2eb04 Compare November 17, 2026 17:46
@cursor cursor Bot added the risk:low label Nov 17, 2026

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

Stale comment

Risk: low.

Automated risk review (dry run): Low

This PR would be automatically approved. Because it was authored by a bot, a human approving review would also be required.

Why: This is a Release Please version bump for LaunchDarkly.ServerSdk 8.18.0 touching only LaunchDarkly.ServerSdk.csproj, .release-please-manifest.json, PROVENANCE.md, and CHANGELOG.md. Cursor Bugbot passed with no findings, and human review is needed with no reviewers assigned because the author is a bot.

If you disagree with this review, share this PR in #feedback-agent-approvals or submit a changes-requested review explaining why.

Open in Web View Automation 

Sent by Cursor Approval Agent: Dry-Run PR Approver

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--LaunchDarkly.ServerSdk branch 5 times, most recently from 6bcf96f to 34ccf63 Compare November 19, 2026 13:27

@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 effort 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 34ccf63. Configure here.

* Clear empty FDv2 selectors in the server SDK ([#407](https://github.com/launchdarkly/dotnet-core/issues/407)) ([c92f5b2](https://github.com/launchdarkly/dotnet-core/commit/c92f5b2db6285eda403cc4d94d591ff23160ef2f))
* Make TestData ValueForAll return its value when targeting is off ([#400](https://github.com/launchdarkly/dotnet-core/issues/400)) ([c8fef92](https://github.com/launchdarkly/dotnet-core/commit/c8fef92a40c9cb307a94704dfb36024e4e6da787))
* Retry a file data load whose read fails, and make the retry tests and the FDv2 fallback test robust to timing ([#395](https://github.com/launchdarkly/dotnet-core/issues/395)) ([741b662](https://github.com/launchdarkly/dotnet-core/commit/741b6628039cb206cfbb81b125a20323998494ab))
* Write a JSON tombstone for deleted items in the DynamoDB store ([#409](https://github.com/launchdarkly/dotnet-core/issues/409)) ([d93f42a](https://github.com/launchdarkly/dotnet-core/commit/d93f42a9a6c8b6cad03482e0d29970b85ef97941))

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

DynamoDB fix in server changelog

Low Severity

The tombstone bullet describes a LaunchDarkly.ServerSdk.DynamoDB change, not LaunchDarkly.ServerSdk. Leaf changelogs keep only notes that apply to that package; shipping 8.18.0 does not include this store fix, so the server notes advertise a behavior change this package does not ship.

Fix in Cursor Fix in Web

Triggered by learned rule: Leaf CHANGELOGs keep only that SDK's notes

Reviewed by Cursor Bugbot for commit 34ccf63. Configure here.

@cursor cursor Bot added risk:medium and removed risk:low labels Nov 19, 2026

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

Risk: medium.

Automated risk review (dry run): Medium

This PR would not be automatically approved. Human approval required.

The earlier Low would-approve decision no longer applies. Human review is needed and no reviewers were assigned.

Why: Cursor Bugbot found an unresolved issue in pkgs/sdk/server/CHANGELOG.md attributing a DynamoDB store tombstone fix to LaunchDarkly.ServerSdk 8.18.0, so this release metadata bump is Medium rather than Low.

If you disagree with this review, share this PR in #feedback-agent-approvals or submit a changes-requested review explaining why.

Open in Web View Automation 

Sent by Cursor Approval Agent: Dry-Run PR Approver

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--LaunchDarkly.ServerSdk branch 4 times, most recently from 40cd8b1 to c877295 Compare November 20, 2026 20:12
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--LaunchDarkly.ServerSdk branch from c877295 to fac2b5a Compare November 20, 2026 23:52

This branch has not been deployed

No deployments
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