3.7.3

[3.7.3] - 2020-10-28

Fixed:

• When using the DynamoDB data store integration with a prefix string, the prefix was being prepended to keys with a slash separator (example: my-prefix/features:my-flag-key). This was inconsistent with the colon separator that is used in the other server-side SDKs (example: my-prefix:features:my-flag-key), making the PHP SDK unable to read flags that were put into the database by other SDKs or by the Relay Proxy, if a prefix was used. This has been fixed to be consistent with the other SDKs. (#138)

3.7.2

[3.7.2] - 2020-04-24

Fixed:

• The SDK could try to send analytics events even if send_events had been set to false. This bug was introduced in the 3.6.0 release.
• A use statement with the wrong namespace was causing Composer to print a deprecation warning. (Thanks, bfenton-smugmug!)

3.7.1

[3.7.1] - 2020-01-03

Fixed:

• Loosened the Monolog dependency constraint so that it will accept either a 1.x or a 2.x version. This should be compatible with all currently supported PHP versions; the SDK's use of Monolog does not rely on any features that are specific to 1.x. (Thanks, mrtus!)
• In rare circumstances (depending on the exact data in the flag configuration, the flag's salt value, and the user properties), a percentage rollout could fail and return a default value, logging the error "Data inconsistency in feature flag ... variation/rollout object with no variation or rollout". This would happen if the user's hashed value fell exactly at the end of the last "bucket" (the last variation defined in the rollout). This has been fixed so that the user will get the last variation.

3.7.0

[3.7.0] - 2019-12-13

Added:

• Added integration with the phpredis extension, which has similar functionality to the already-supported predis but may have better performance (since predis is written in pure PHP, whereas phpredis uses a C extension). See LaunchDarkly::Integrations::PHPRedis. (Thanks, nicofff!)

3.6.0

[3.6.0] - 2019-10-01

Added:

• Added support for upcoming LaunchDarkly experimentation features. See LDClient.track.

3.5.5

[3.5.5] - 2019-06-05

Fixed:

• The SDK could throw an exception when calling allFlagsState() if APC/APCu caching was enabled. This bug was introduced in the 3.5.0 release. (Thanks, omnicolor!)
• Improved unit test coverage for the caching logic.

3.5.4

[3.5.4] - 2019-05-10

Changed:

• Changed the package name from launchdarkly/launchdarkly-php to launchdarkly/server-sdk

There are no other changes in this release. Substituting launchdarkly/launchdarkly-php version 3.5.3 with launchdarkly/server-sdk version 3.5.4 will not affect functionality.

3.5.3

[3.5.3] - 2019-04-26

Fixed:

• Segment rollout calculations did not work correctly if the rollout was based on a user attribute other than key; all users would end up in the same bucket. (Thanks, m6w6!)
• Running the SDK unit tests is now simpler, as the database integrations can be skipped. See CONTRIBUTING.md.

Note on future releases

The LaunchDarkly SDK repositories are being renamed for consistency. This repository is now php-server-sdk rather than php-client.

The package name will also change. In the 3.5.3 release, it is still launchdarkly/launchdarkly-php; in all future releases, it will be launchdarkly/server-sdk. No further updates to the launchdarkly/launchdarkly-php package will be published after this release.

3.5.2

[3.5.2] - 2019-04-11

Fixed:

• In the 3.5.1 release, the VERSION constant was incorrectly still reporting the version as "3.5.0". The constant is now correct. There are no other changes in this release.

3.5.1

[3.5.1] - 2019-04-03

Fixed:

• Setting user attributes to non-string values when a string was expected would cause analytics events not to be processed. The SDK will now convert attribute values to strings as needed.
• If track or identify is called without a user, the SDK now logs a warning, and does not send an analytics event to LaunchDarkly (since it would not be processed without a user).