Skip to content

@hroederld hroederld released this Jul 30, 2019

[1.5.0] - 2019-07-26

Added

  • Added the LDUserFree function. This can be used to free a user object before it has been passed to the client

Fixed

  • A leak of HTTP headers set for requests to LaunchDarkly
  • A leak of the in memory flag store when LDClientIdentify is called. This was introduced in 1.2.0
  • A leak of a structure when events are flushed but no events need to be sent
Assets 10

@hroederld hroederld released this Jul 3, 2019 · 1 commit to master since this release

[1.4.0] - 2019-07-03

Added

  • Added the LDConfigSetVerifyPeer configuration option. This option allows disabling certificate verification, which may be useful for testing, or in unfortunate networking configurations. Note that certificate verification should not be disabled unless it is essential, as it makes the SDK vulnerable to man-in-the-middle attacks. (Thanks, mstrater!)
Assets 10

@hroederld hroederld released this Jun 21, 2019 · 3 commits to master since this release

[1.3.2] - 2019-06-20

Fixed

  • Fixed a bug where reconnecting in streaming mode sometimes erroneously waited for a timeout when switching users
Assets 10

@hroederld hroederld released this May 10, 2019 · 404 commits to master since this release

[1.3.1] - 2019-05-10

Changed:

  • Renamed the build artifacts. They are now prefixed with ldclientapi.
  • Changed repository references to use the new URL.

There are no other changes in this release. Substituting the build artifacts from version 1.3.0 with the build artifacts from version 1.3.1 will not affect functionality.

Assets 10

@hroederld hroederld released this Apr 19, 2019 · 407 commits to master since this release

[1.3.0] - 2019-04-18

Added:

  • Version string macro LD_SDK_VERSION in ldapi.h
Assets 10

@hroederld hroederld released this Apr 16, 2019 · 408 commits to master since this release

[1.2.2] - 2019-04-16

Fixed:

  • Ensure LDSetLogFunction is properly exported in shared libraries
Assets 10

@hroederld hroederld released this Apr 12, 2019 · 409 commits to master since this release

[1.2.1] - 2019-04-12

Fixed:

  • Cleaned up exported symbols in shared libraries
Assets 10

@hroederld hroederld released this Apr 12, 2019 · 410 commits to master since this release

[1.2.0] - 2019-04-11

Added:

  • Added multiple environments support. It is now possible to evaluate flags in additional environments. You can add multiple secondary environments with LDConfigAddSecondaryMobileKey, and use an environment with LDClientGetForMobileKey.
  • Added LDNodeAppendHash, and LDNodeAppendArray
  • Exposed LDConfigFree (not needed in standard usage)

Fixed:

  • Switched to bitflag comparison routines as per cJSON doc
  • Memory leak of background thread stack
Assets 10

@hroederld hroederld released this Mar 5, 2019 · 412 commits to master since this release

[1.1.1] - 2019-03-05

Added:

  • Improved Windows build documentation
  • Added logging on authorization failure

Fixed

  • A deadlock manifesting on Windows systems
Assets 10

@eli-darkly eli-darkly released this Feb 2, 2019 · 413 commits to master since this release

[1.1.0] - 2019-02-01

Added:

  • It is now possible to obtain information about how each feature flag value was determined (did the user match a target list or a rule, was the flag turned off, etc.). To do this, add LDConfigSetUseEvaluationReasons(config, true) to your configuration, and then call LD____VariationDetail instea of LD____Variation when evaluating a flag. The "Detail" functions will fill in an LDVariationDetails struct whose reason field is a JSON data structure. See DOCS.md and the SDK reference guide on "Evaluation reasons".
Assets 10
You can’t perform that action at this time.