4.2.1

[4.2.1] - 2022-07-05

Changed:

• Expanded lower version restriction on Guzzle.

4.2.0

[4.2.0] - 2022-04-13

Added:

• Add support for psr/log v2 and v3.
• The LaunchDarkly\Integrations\TestData is a new way to inject feature flag data programmatically into the SDK for testing—either with fixed values for each flag, or with targets and/or rules that can return different values for different users. Unlike LaunchDarkly\Integrations\Files, this mechanism does not use any external resources, only the data that your test code has provided.

4.1.0

[4.1.0] - 2022-02-16

Added:

• The curl command used for publishing events will now honor the connect_timeout parameter.
• Publishing events on Windows will now use PowerShell and Invoke-WebRequest instead of curl.

Fixed:

• Numeric strings are no longer treated like numbers in equality checks.
• User attributes with values of 0 or false will no longer be filtered out of event payloads.
• When using allFlagsState to produce bootstrap data for the JavaScript SDK, the PHP SDK was not returning the correct metadata for evaluations that involved an experiment. As a result, the analytics events produced by the JavaScript SDK did not correctly reflect experimentation results.

4.0.0

[4.0.0] - 2021-08-06

This major version release is for updating PHP compatibility, simplifying the SDK's dependencies, and removing deprecated names.

Except for the dependency changes described below which may require minor changes in your build, usage of the SDK has not changed in this release. For more details about changes that may be necessary, see the 3.x to 4.0 migration guide.

Dropping support for obsolete PHP versions makes it easier to maintain the SDK and keep its dependencies up to date. See LaunchDarkly's End of Life Policy regarding platform version support.

Simplifying dependencies by moving optional integration features into separate packages reduces the size of the SDK bundle, as well as reducing potential compatibility problems and vulnerabilities.

Added:

• Added type declarations to all methods. These could result in a TypeError at runtime if you have been passing values of the wrong types to SDK methods (including passing a null value for a parameter that should not be null)-- although in most cases, this would have caused an error anyway at some point in the SDK code, just not such a clearly identifiable error. To detect type mistakes before runtime, you can use a static analysis tool such as Psalm.

Changed:

• The minimum PHP version is now 7.3.
• Updated many dependencies to newer versions and/or more actively maintained packages.

Removed:

• Removed the bundled Redis, DynamoDB, and Consul integrations. These are now provided as separate packages; see php-server-sdk-redis-predis, php-server-sdk-redis-phpredis, php-server-sdk-dynamodb, and php-server-sdk-consul.
• Removed all types and methods that were deprecated in the last 3.x version.
• Removed implementation types from the \LaunchDarkly namespace that were annotated as @internal and not documented, such as types that are part of the internal feature data model. These are not meant for use by application code, and are always subject to change. They have been moved into \LaunchDarkly\Impl.

3.9.1

[3.9.1] - 2021-08-02

Fixed:

• The phpredis integration was ignoring the phpredis_client option for passing in a preconfigured Redis client. (Thanks, CameronHall!)

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 to LDClient. 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.5] - 2021-03-01

Fixed:

• PHPRedis::featureRequester was not recognizing the phpredis_client option. (Thanks, riekelt!)

3.7.4

[3.7.4] - 2021-01-07

Fixed:

• Fixed a warning message which erroneously referred to the wrong method.