Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 5.3.1 #232

Merged
merged 282 commits into from
Dec 16, 2020
Merged

Release 5.3.1 #232

merged 282 commits into from
Dec 16, 2020

Conversation

torchhound
Copy link
Contributor

[5.3.1] - 2020-12-15

Fixed

  • Decoupled FlagStore from LDUser to fix a bug where multiple environments could overwrite each other's flag values.

…hanged TimeInterval to Date, changed two inout's to var's
Rebuilt Connection Status, added unit tests, fixed warnings
gwhelanLD and others added 25 commits July 17, 2020 12:16
Also removed unused test code. Improve documentation on LDClient.flush()
)

Fix a bug with preventing the SDK from retrying eventsource connections when the service returns a 5XX error code. Renamed a couple of public APIs. Removed some publicly exposed implementation details. Updated CHANGELOG.md for 5.0.
Allow dynamic configuration of http headers through LDConfig.headerDelegate
…130)

* Removed FlagStore from LDUser

* All unit tests build and LDClientSpec doesn't crash

* Fixed 1 unit test, removed unnecessary testing parameter in internalIdentify

* Fixed 29 unit tests

* Fixed 26 unit tests

* Fix all but 4 unit tests

* Removed comment

* Addressed PR feedback

* Removed unnecessary for each in LDUserSpec

* Removed unnecessary contexts in LDUserSpec, removed user value in FlagChangeNotifierSpec

* Fixed LDUserSpec context, added stub flags to DarklyServiceSpec

* Make LDClientSpec init less hacky

* Clear FlagStore if new user does not have cached flags, make flagStore a let

* Added FlagStore back to LDUser for init from flag dictionary, check for user.flagStore on LDClient init and identify

* Added deprecation comment to dictionary init for LDUser, prioritize LDUser FlagStore over cache in identify

* Changed identify ordering back to cache over flagstore, made FlagStore a let
@torchhound torchhound merged commit 89dcc5d into v5 Dec 16, 2020
@torchhound torchhound deleted the release-5.3.1 branch December 16, 2020 00:22
keelerm84 added a commit that referenced this pull request Jun 5, 2023
TLS 1.1 has been deprecated for a long time and has been dropped by most
major providers. The LaunchDarkly APIs haven't accepted anything lower
than TLS 1.2 for a long time.

We are therefore forcing TLS 1.2 as the minimum going forward in this
library.
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.

4 participants