chore(main): release LaunchDarkly.ClientSdk 5.7.2#265
Merged
tanderson-ld merged 1 commit intoMay 26, 2026
Merged
Conversation
tanderson-ld
approved these changes
May 26, 2026
Contributor
Author
|
🤖 Created releases: 🌻 |
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
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.
🤖 I have created a release beep boop
5.7.2 (2026-05-26)
Bug Fixes
This PR was generated with Release Please. See documentation.
Note
Low Risk
Mechanical version and changelog updates with no code in the diff; runtime change is a targeted compatibility fix already described in the release notes.
Overview
This PR is a Release Please cut for LaunchDarkly.ClientSdk 5.7.2. It bumps the package version everywhere release tooling expects it:
.release-please-manifest.json,LaunchDarkly.ClientSdk.csproj,CHANGELOG.md, andPROVENANCE.md(exampleSDK_VERSIONfor attestation verification).The changelog entry records the user-facing fix from #264: gracefully handle MAUI unavailability in non-MAUI Windows apps—so desktop/WinUI apps that target
net8.0-windowswithout a full MAUI stack should not fail when MAUI APIs are absent. No source changes appear in this diff; only release metadata and version strings.Reviewed by Cursor Bugbot for commit c9f96af. Bugbot is set up for automated code reviews on this repo. Configure here.