Releases: optimizely/go-sdk
Releases · optimizely/go-sdk
Release v1.0.0-beta3
[1.0.0-beta3] - October 15th, 2019
Breaking Changes
- Refactored EventProcessor and ConfigManager components to no longer require an ExecutionContext be passed in during construction. It will be injected into them by the client factory. #130
- Moved the entire
optimizely
package fromgithub.com/optimizely/go-sdk/optimizely
togithub.com/optimizely/go-sdk/pkg
to better follow convention and best practices. #135
Release v1.0.0-beta2
[1.0.0-beta2] - October 2nd, 2019
New Features
- Introduces the
Activate
andGetVariation
APIs for running A/B tests. - Makes the top-level client components public:
DecisionService, ConfigManager, EventProcessor
.
1.0.0-beta1
[1.0.0-beta1] - September 27th, 2019
New Features
- Added decision listeners and project config update listeners.
- Added optional configuration parameters to NewProcessor.
Breaking Changes
- This method
OptimizelyFactory.ClientWithOptions()
has been removed in favor ofOptimizelyFactory.Client(clientOptions ...OptionFunc)
Release v0.2.0
[0.2.0] - September 11th, 2019
This release of the SDK introduces Feature Management capabilities for running both Feature Rollouts as well as Feature Tests using Optimizely Feature Management.
New Features
- Introduces feature variable getters via
GetFeatureVariable*
for parameterizing your feature tests. - Introduces the
Track
API call for sending conversion events to Optimizely. - The
IsFeatureEnabled
API will now send impression events if there is a feature test attached to the feature being accessed.
Breaking Changes
- Vendored packages have been removed in favor of declaring dependencies and their versions using
go.mod
.
Release 0.1.0
[0.1.0-beta] - August 23rd, 2019
This is the initial release of the SDK, which includes support for running Feature Rollouts using Optimizely Feature Management.
New Features
- Introduces the
IsFeatureEnabled
andGetFeatureEnabled
APIs for determining whether the feature is enabled for a user or not. Please see our README.