Releases: launchdarkly/php-server-sdk
Releases · launchdarkly/php-server-sdk
3.9.0
[3.9.0] - 2021-06-21
Added:
- The SDK now supports the ability to control the proportion of traffic allocation to an experiment. This works in conjunction with a new platform feature now available to early access customers.
3.8.0
[3.8.0] - 2021-04-19
Added:
- Added the
alias
method toLDClient
. This can be used to associate two user objects for analytics purposes with an alias event.
3.7.6
[3.7.6] - 2021-04-14
Fixed:
- When using
Files.featureRequester
, if a data file did not contain valid JSON, the SDK would throw a PHP syntax error instead of the expected "File is not valid JSON" error. (Thanks, GuiEloiSantos!)
3.7.5
3.7.4
[3.7.4] - 2021-01-07
Fixed:
- Fixed a warning message which erroneously referred to the wrong method.
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:
3.6.0
[3.6.0] - 2019-10-01
Added:
- Added support for upcoming LaunchDarkly experimentation features. See
LDClient.track
.