chore(main): release launchdarkly_common_client 1.14.0

[LaunchDarklyReleaseBot]

🤖 I have created a release beep boop

1.14.0 (2026-06-16)

Features

• Add FDv2 payload application via FlagManager.applyChanges (#299) (66c2554)
• Add FDv2 payload handling to the data source event handler (#305) (761ed9d)
• Add FDv2 source manager (#298) (43d899e)
• Add FDv2 streaming source factories and query-parameter authentication (7b46ac6)
• Add FDv2 synchronizer fallback and recovery conditions (#297) (17f7b4e)
• Centralize platform credential handling in CredentialConfig (#300) (c677c3d)
• Translate FDv2 payloads at the data source layer (7b46ac6)
• Update launchdarkly_event_source_client to version 2.2.0 (#302) (cb6a5c0)

Bug Fixes

• Close the final initializer on exhaustion; document the source manager contract (#304) (b20c35e)

---

This PR was generated with Release Please. See documentation.

---

Note

Low Risk
Only version and changelog/manifest updates; runtime behavior is unchanged in this PR.

Overview
Release-only PR for launchdarkly_common_client 1.14.0: updates pubspec.yaml, .release-please-manifest.json, and adds the 1.14.0 section to CHANGELOG.md. No application code changes in this diff.

The new changelog entry documents work already merged on main—end-to-end FDv2 data sourcing (source manager, streaming factories, payload translation and FlagManager.applyChanges, synchronizer fallback/recovery), CredentialConfig-centralized auth (including query-param auth for streaming), launchdarkly_event_source_client 2.2.0, and a fix to close the final initializer when exhausted.

^{Reviewed by Cursor Bugbot for commit 04842e1. Bugbot is set up for automated code reviews on this repo. Configure here.}

[kinyoklion]

I am holding this PR. Releases are in a working state, but we don't have a need to release each intermediate change.