Release 4.2.2

[4.2.1] - October 7, 2025

Fixed

• Fixed Go module dependencies synchronization to enable
  successful Docker builds

This release contains the same functionality as v4.2.1 (secure
environment SDK key support for decision notifications), but
with properly synchronized Go module dependencies that enable
successful builds and Docker image creation.

Release 4.3.0-beta.1

New Features (Beta)

• Redis Streams for Persistent Notification Delivery
  (#444): Added Redis Streams implementation as an alternative to Redis Pub/Sub for notification synchronization across Agent nodes.
  Redis Streams provides:

  • Persistent message delivery with acknowledgment
  • Automatic retries with exponential backoff
  • Consumer groups for load balancing
  • Configurable batching and flush intervals
  • Connection error recovery with reconnection logic
  • Comprehensive metrics tracking

  Configure via synchronization.notification.default: "redis-streams" in config.yaml. See documentation for configuration options including batch_size, flush_interval, max_retries, and connection_timeout.

Fixed

• Fixed flexible Redis password configuration to support auth_token, redis_secret, and password fields with environment variable fallback (#444)

Release 4.2.1

[4.2.1] - September 3, 2025

Fixed

• Fixed decision notifications not working with secure environment SDK keys
• Added documentation for Redis channel naming pattern in config.yaml
• PR 441

---

Additional Technical Details

Features

• Secure token parsing: Handle SDK keys with secure tokens in format sdkKey:apiKey for notification endpoints
• Enhanced notification handler to extract SDK key from secure token format

Bug Fixes

• Fixed notification handler test hanging issues
• Updated Go version to 1.23 for better compatibility
• Updated Alpine Docker base image from 3.21 to 3.20 for Go 1.23 compatibility
• Fixed test timeouts and formatting

Documentation

• Improved Redis subscription documentation in config.yaml
• Added comprehensive unit tests for secure token parsing (7 test cases)

Full Changelog: v4.2.0...v4.2.1

Release 4.2.0

What's Changed

• [FSSDK-10665] fix: Github Actions YAML files vulnerable to script injections corrected by @FarhanAnjum-opti in #425
• [FSSDK-10734] update regex to allow = character by @pulak-opti in #426
• [FSSDK-10734] update regex to support base64 char for SDK Key & access token by @pulak-opti in #427
• chore(deps): bump golang.org/x/crypto from 0.19.0 to 0.31.0 by @junaed-optimizely in #429
• [FSSDK-11338] Resolve critical SCA prisma alerts by @Mat001 in #430
• [FSSDK-11471] HIGH Dependabot Alerts- Golang/Agent by @Mat001 in #433
• [FSSDK-11452] Agent - netspring integration - experimentID, VariationID by @Mat001 in #438

New Contributors

• @FarhanAnjum-opti made their first contribution in #425
• @junaed-optimizely made their first contribution in #429

Full Changelog: v4.1.0...v4.2.0

Release 4.1.0

[4.1.0] - August 29, 2024

New Features

• Moderate & high CVEs are fixed. (#414,#416)
• Log levels are changed to Debug and redundant info logs are removed to make /decide API call less noisy. (#420)
• isEveryoneElseVariation field is added in /decide API response. (#422)

Release 4.0.0

[4.0.0] - January 22, 2024

New Features

The 4.0.0 release introduces a new primary feature, Advanced Audience Targeting enabled through integration with Optimizely Data Platform (ODP) (#356, #364, #365, #366).

You can use ODP, a high-performance Customer Data Platform (CDP), to easily create complex real-time segments (RTS) using first-party and 50+ third-party data sources out of the box. You can create custom schemas that support the user attributes important for your business, and stitch together user behavior done on different devices to better understand and target your customers for personalized user experiences. ODP can be used as a single source of truth for these segments in any Optimizely or 3rd party tool.

With ODP accounts integrated into Optimizely projects, you can build audiences using segments pre-defined in ODP. The SDK will fetch the segments for given users and make decisions using the segments. For access to ODP audience targeting in your Feature Experimentation account, please contact your Optimizely Customer Success Manager.

This version includes the following changes:

• FetchQualifiedSegments() API has been added to the /decide endpoint. This API will retrieve user segments from the ODP server. The fetched segments will be used for audience evaluation. Fetched data will be stored in the local cache to avoid repeated network delays.

• SendOdpEvent() API has been added with the /send-opd-event endpoint. Customers can build/send arbitrary ODP events that will bind user identifiers and data to user profiles in ODP.

For details, refer to our documentation pages:

• Advanced Audience Targeting

• Server SDK Support

• Use Optimizely Agent

• Configure Optimizely Agent

This release also introduces a fundamental enhancement to the agent with the addition of a datafile syncer. This feature is designed to facilitate seamless synchronization of datafiles across agent nodes, ensuring consistency and accuracy in the operation of the webhook API.
The datafile syncer uses a PubSub system (Default: Redis) to send updated datafile webhook notification to Agent nodes (in HA system) so that nodes can immediately fetch the latest datafile. (#405)

Breaking Changes

• ODPManager in the SDK is enabled by default. Unless an ODP account is integrated into the Optimizely projects, most ODPManager functions will be ignored. If needed, ODPManager can be disabled when OptimizelyClient is instantiated. From Agent, it can be switched off from config.yaml or env variables.
• Updated go-sdk version to v2.0.0 with module path github.com/optimizely/go-sdk/v2

Functionality Enhancement

• Updated openapi schema to 3.1.0. (#392)
• Added support for prometheus metrics. (#348)
• Github Issue template is udpated. (#396)
• Updated go version to 1.21. (#398)
• Added OpenTelemetry Tracing Support. (#400)
• Added traceID & spanID to logs. (#407)

Bug fixes

In previous versions, there was an issue where the Notification API would miss notification events when the Agent was operating in HA mode. It only got notification events from one Agent node. The bug has been addressed in this release with the implementation of a comprehensive solution. A PubSub system (Default: Redis) is used to ensure consistent retrieval of notification events across all nodes in an HA setup. (#399)

Release 3.2.0

[3.2.0] - December 13, 2023

New Features

• Added support for including traceId and spanId into the logs. (#407)

Release 3.1.0

[3.1.0] - November 3, 2023

• Added support for Prometheus-based metrics alongside expvar metrics. This can be configured from the config.yaml file. (#348)

• Added support for OpenTelemetry tracing. Distributed tracing is also supported according to W3C TraceContext. (#400, #401, #402)

Release 4.0.0-beta

[4.0.0-beta] - May 11, 2023

New Features

The 4.0.0-beta release introduces a new primary feature, Advanced Audience Targeting enabled through integration with Optimizely Data Platform (ODP) (#356, #364, #365, #366).

You can use ODP, a high-performance Customer Data Platform (CDP), to easily create complex real-time segments (RTS) using first-party and 50+ third-party data sources out of the box. You can create custom schemas that support the user attributes important for your business, and stitch together user behavior done on different devices to better understand and target your customers for personalized user experiences. ODP can be used as a single source of truth for these segments in any Optimizely or 3rd party tool.

With ODP accounts integrated into Optimizely projects, you can build audiences using segments pre-defined in ODP. The SDK will fetch the segments for given users and make decisions using the segments. For access to ODP audience targeting in your Feature Experimentation account, please contact your Optimizely Customer Success Manager.

This version includes the following changes:

• FetchQualifiedSegments() API has been added to the /decide endpoint. This API will retrieve user segments from the ODP server. The fetched segments will be used for audience evaluation. Fetched data will be stored in the local cache to avoid repeated network delays.

• SendOdpEvent() API has been added with the /send-opd-event endpoint. Customers can build/send arbitrary ODP events that will bind user identifiers and data to user profiles in ODP.

For details, refer to our documentation pages:

• Advanced Audience Targeting

• Server SDK Support

• Use Optimizely Agent

• Configure Optimizely Agent

Breaking Changes

• ODPManager in the SDK is enabled by default. Unless an ODP account is integrated into the Optimizely projects, most ODPManager functions will be ignored. If needed, ODPManager can be disabled when OptimizelyClient is instantiated. From Agent, it can be switched off from config.yaml or env variables.

Release 3.0.1

[3.0.1] - March 16, 2023

• Update README.md and other non-functional code to reflect that this SDK supports both Optimizely Feature Experimentation and Optimizely Full Stack. (#369).