fix: Update launchdarkly_dart_common to version 1.8.2 - #338
Merged
Merged
Conversation
kinyoklion
approved these changes
Aug 26, 2026
tanderson-ld
pushed a commit
that referenced
this pull request
Aug 26, 2026
🤖 I have created a release *beep* *boop* --- ## [1.14.3](launchdarkly_common_client-v1.14.2...launchdarkly_common_client-v1.14.3) (2026-08-26) ### Bug Fixes * include flagVersion when serializing flag evaluations ([#335](#335)) ([6fca7f9](6fca7f9)) * Update launchdarkly_dart_common to version 1.8.2 ([#338](#338)) ([38dd034](38dd034)) --- 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 bookkeeping** for `launchdarkly_common_client` **1.14.3**: bumps the package version in `pubspec.yaml`, updates `.release-please-manifest.json`, and adds the **1.14.3** section to `CHANGELOG.md`. > > This release tags two bug fixes already on `main`: serialized flag evaluations now include **`flagVersion`**, and the package is aligned with **`launchdarkly_dart_common` 1.8.2**. The PR diff does not contain application code—only version and changelog updates from Release Please. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 1304ba5. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
tanderson-ld
added a commit
that referenced
this pull request
Aug 26, 2026
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). <!-- CURSOR_SUMMARY --> --- > [!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. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 77ff98a. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
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.
Propagates the
flagVersionserialization fix (#335, released aslaunchdarkly_dart_common1.8.2 in #337) down tolaunchdarkly_common_client.common_clientpinslaunchdarkly_dart_commonexactly, so the fix does not reach it without this edit. Without this bump, the pendingcommon_client1.14.3 release (#336) would ship a changelog crediting the fix while still resolving 1.8.1, which does not contain it — the fix lives entirely inpackages/common.Landing this before #336 merges folds the commit into that release, so 1.14.3 genuinely carries the fix.
Next hop after this: bump
launchdarkly_common_clientinpackages/flutter_client_sdk/pubspec.yamlto 1.14.3, which produces the Flutter SDK release users actually consume.Same shape as the prior propagation commits: 0e5301d (
fix: Update launchdarkly_dart_common to version 1.8.1, #277) and 48f6790 (fix: Update launchdarkly_common_client to version 1.14.2, #331).Note: CI resolves
commonthrough the melos path override (melos bs), so it passes independently of pub.dev. Thecommon_clientpublish does require 1.8.2 to be live on pub.dev, so #336 should merge only after the 1.8.2 publish run completes.Note
Overview
Bumps the pinned
launchdarkly_dart_commondependency inlaunchdarkly_common_clientfrom 1.8.1 to 1.8.2, so the client package actually picks up theflagVersionserialization fix shipped in common.Because
common_clientuses an exact version pin, the fix does not flow through until this change; it aligns the dependency with the upcoming 1.14.3 release so published artifacts match the credited bug fix.Reviewed by Cursor Bugbot for commit 1bc6969. Bugbot is set up for automated code reviews on this repo. Configure here.