fix: bump LaunchDarkly.InternalSdk pins to 3.10.1 - #343
Merged
Conversation
Picks up the monotonic clock fix for repeating-task intervals and stream-init durations, and UTC diagnostic event timestamps. Co-Authored-By: tanderson@launchdarkly.com <tanderson@launchdarkly.com>
Picks up the monotonic clock fix for repeating-task intervals and stream-init durations, and UTC diagnostic event timestamps. The pin was three minors behind, so this also brings gzip AutomaticDecompression on the default HTTP handler, anonymous context attribute redaction in all events, and the net8.0 target framework update. Co-Authored-By: tanderson@launchdarkly.com <tanderson@launchdarkly.com>
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
tanderson-ld
marked this pull request as ready for review
September 2, 2026 20:31
jsonbailey
approved these changes
Sep 2, 2026
This was referenced Sep 2, 2026
tanderson-ld
pushed a commit
that referenced
this pull request
Sep 2, 2026
🤖 I have created a release *beep* *boop* --- ## [8.16.1](LaunchDarkly.ServerSdk-v8.16.0...LaunchDarkly.ServerSdk-v8.16.1) (2026-09-02) ### Bug Fixes * bump LaunchDarkly.InternalSdk pins to 3.10.1 ([#343](#343)) ([fa7bcf9](fa7bcf9)) * Retry after partial file reads. ([#218](#218)) ([93f4508](93f4508)) * use monotonic clock for intervals and durations, UTC for diagnostic timestamps ([#339](#339)) ([e12ee4a](e12ee4a)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Overview** > **Release Please** bumps **LaunchDarkly.ServerSdk** from **8.16.0** to **8.16.1** in the manifest, `LaunchDarkly.ServerSdk.csproj`, provenance docs, and changelog. > > This PR does not change SDK source; it cuts the **8.16.1** patch release and documents three bug fixes already on `main`: **LaunchDarkly.InternalSdk** pinned to **3.10.1**, retries after **partial file reads** (file data source), and **monotonic clock** for intervals/durations plus **UTC** for diagnostic timestamps. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit fd96aee. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
#339 fixed the monotonic-clock and UTC-timestamp bugs in
LaunchDarkly.InternalSdk, released as 3.10.1 (#341), but neither SDK consumes it: both referenceLaunchDarkly.InternalSdkbyPackageReferenceoutsideDebugLocalReferences, so the fix reaches customers only once these pins move.Two commits, because the two pins are not equivalent moves:
fix:) — 3.10.0 -> 3.10.1, the patch itself and nothing else.feat:) — the pin was three minors behind, so this also picks up 3.8.0 (net8.0 target framework update), 3.9.0 (anonymous context attribute redaction in all events), and 3.10.0 (gzipAutomaticDecompressionon the default HTTP handler). The last one changes runtime behavior for every client SDK user, which is why this commit is afeat:rather than folding into the pending 5.9.7 patch.Verified against the published 3.10.1 (not a project reference —
project.assets.jsonresolvesLaunchDarkly.InternalSdk/3.10.1in bothsrc/obj): server 1605 tests and client 380 tests pass, server builds fornetstandard2.0;net462;net8.0, client fornetstandard2.0;net8.0.The squash merge collapsed both commits under the
fix:PR title, so release-please cut the client as a 5.9.7 patch with no note of the absorbed behavior changes. The override below re-types the merged commit as a feature.LaunchDarkly.ServerSdk8.16.1 is already tagged and includes this commit, so the override only affects the pending client release.BEGIN_COMMIT_OVERRIDE
feat: bump LaunchDarkly.InternalSdk pins to 3.10.1
The client SDK pin moved from 3.7.0, so it also picks up gzip
AutomaticDecompressionon the default HTTP handler, anonymous context attribute redaction in events, and the net8.0 target framework update.END_COMMIT_OVERRIDE