Skip to content

fix: Update launchdarkly_common_client to version 1.14.3 - #339

Merged
tanderson-ld merged 1 commit into
mainfrom
ta/bump-common-client-1.14.3
Aug 26, 2026
Merged

tanderson-ld merged 1 commit into
mainfrom
ta/bump-common-client-1.14.3

Conversation

@tanderson-ld

@tanderson-ld tanderson-ld commented Aug 26, 2026 •

Copy link
Copy Markdown
Contributor

Final hop propagating the flagVersion serialization fix (#335) out to the published Flutter SDK.

flutter_client_sdk pins launchdarkly_common_client exactly, so the fix does not reach SDK users without this edit. This is the only place in the repo pinning common_client.

Chain so far:

Package Version Status
launchdarkly_dart_common 1.8.2 published — contains the fix (#335, #337)
launchdarkly_common_client 1.14.3 published — pins common 1.8.2 (#338, #336)
launchdarkly_flutter_client_sdk 4.20.3 this PR triggers the release

1.14.3 is already live on pub.dev, so there is no publish-ordering constraint: this can merge as soon as CI is green, and the resulting 4.20.3 release PR after it.

Same shape as the prior propagation commits: 48f6790 (fix: Update launchdarkly_common_client to version 1.14.2, #331) and 0e5301d (fix: Update launchdarkly_dart_common to version 1.8.1, #277).


Note

Overview
Bumps the exact launchdarkly_common_client pin in flutter_client_sdk from 1.14.2 to 1.14.3 so published Flutter SDK users pick up the upstream fix for flagVersion in flag evaluation serialization (via launchdarkly_dart_common 1.8.2).

No Dart/Flutter source changes—only pubspec.yaml. This is the last hop in the version propagation chain before a 4.20.3 Flutter SDK release.

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

BEGIN_COMMIT_OVERRIDE
fix: Update launchdarkly_common_client to version 1.14.3
fix: Includes fix for flagVersion tracking in events
END_COMMIT_OVERRIDE

@tanderson-ld
tanderson-ld requested a review from a team as a code owner August 26, 2026 19:27
@tanderson-ld
tanderson-ld merged commit aaa2f0b into main Aug 26, 2026
9 checks passed
@tanderson-ld
tanderson-ld deleted the ta/bump-common-client-1.14.3 branch August 26, 2026 19:35
kinyoklion added a commit that referenced this pull request Sep 25, 2026
## Summary

Propagates `usePost` support for FDv2 polling and streaming requests
(#341) out to the published Flutter SDK.

`flutter_client_sdk` pins `launchdarkly_common_client` exactly, so the
new `DataSystemConfig.usePost` option does not reach SDK users until
this pin moves. This is the only place in the repo that pins
`common_client`.

| Package | Version | Status |
| --- | --- | --- |
| `launchdarkly_common_client` | 1.15.0 | published to pub.dev (#343) |
| `launchdarkly_flutter_client_sdk` | 4.21.0 | this PR triggers the
release |

1.15.0 is live on pub.dev and `flutter pub get` resolves against it, so
there is no publish-ordering constraint: this can merge as soon as CI is
green, and the resulting release PR after it. The commit is a `feat`
because the SDK gains a new configuration option.

Same shape as the prior propagation commits: #339
(`launchdarkly_common_client` 1.14.3) and #331 (1.14.2).

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Overview**
> Bumps the pinned **`launchdarkly_common_client`** dependency from
**1.14.3** to **1.15.0** in `flutter_client_sdk`, so published Flutter
SDK consumers pick up the new **`DataSystemConfig.usePost`** option for
FDv2 polling and streaming (already in common client 1.15.0 on pub.dev).
> 
> There are no other source changes in this PR—only the dependency pin
update, matching prior propagation releases.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
7a2bc06. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants