fix(deps): update dependency @optimizely/react-sdk to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@optimizely/react-sdk	^2.9.1 -> ^3.0.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

optimizely/react-sdk (@​optimizely/react-sdk)

v3.2.2

Compare Source

Bug fixes

• Multiple instances of the Logger make the log system unconfigurable - bug fix. (#​276)

v3.2.1

Compare Source

Bug fixes

• clientReady is true even though internal client promise returns success == false bug fix(#​273)
• useDecision hook set the update listener on overy render bug fix(#​273)
• setForcedDecision does not reflect the changes in optmizely instance and useDecision hook bug fix(#​274)

Changed

• Performance improvements in both hooks and client instance(#​273, #​274)

v3.2.0

Compare Source

New Features

• The new useTrackEvent hook is now available for tracking events within functional components. This hook offers all the existing track event functionalities provided by the SDK. (#​268)

v3.1.2

Compare Source

Changed

• JS SDK bump up for react native polyfill support (#​266)

v3.1.1

Compare Source

Bug Fixes

• ODP integration error. (#​262)

v3.1.0

Compare Source

Bug Fixes

• Error initializing client. The core client or user promise(s) rejected.
  (#​255)
• Unable to determine if feature "{your-feature-key}" is enabled because User ID is not set(#​255)

Changed

• Bumped Optimizely JS SDK version in use (#​255)
• Resolve dependabot dependency vulnerabilities (#​245, #​247, #​248, #​251, #​253)
• Add node versions during testing (#​249)

v3.0.1

Compare Source

Changed

• Updated @optimizely/optimizely-sdk to version 5.0.1 (#​242)
• Updated Dependabot alerts (#​239, #​241)

v3.0.0

Compare Source

New Features

The 3.0.0 release introduces a new primary feature, Advanced Audience Targeting enabled through integration with Optimizely Data Platform (ODP) (
#​229,
#​214,
#​213,
#​212,
#​208,
#​207,
#​206,
#​205,
#​201,
#​200,
#​199)

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 Customer Success Manager.

This release leverages the Optimizely JavaScript SDK 5+

This version includes the following changes:

• New APIs added to ReactSDKClient:

  • fetchQualifiedSegments(): this API will retrieve user segments from the ODP server. The fetched segments will be used for audience evaluation. The fetched data will be stored in the local cache to avoid repeated network delays.

  • getUserContext(): get the current OptimizelyUserContext object in use at the React SDK level.

  • getVuid(): provides access to the anonymous client-side visitor ID (VUID) generated by the JS SDK. This ID is used to identify unique visitors in Optimizely Results in the absence of a standard user ID.

  • sendOdpEvent(): 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

• Client SDK Support

• Initialize React SDK

• Advanced Audience Targeting segment qualification methods

• Send Optimizely Data Platform data using Advanced Audience Targeting

Breaking Changes

• Dropped support for the following browser versions.
  • All versions of Microsoft Internet Explorer.
  • Chrome versions earlier than 102.0.
  • Microsoft Edge versions earlier than 84.0.
  • Firefox versions earlier than 91.0.
  • Opera versions earlier than 76.0.
  • Safari versions earlier than 13.0.
• Dropped support for Node JS versions earlier than 16.

Changed

• Updated @optimizely/optimizely-sdk to version 5.0.0 (#​230).
• Removed use of deprecated @optimizely/js-sdk-* packages.
• Minor version bumps to dependencies.

Bug Fixes

• Updated OptimizelyProvider to (#​229)
  • correctly adhere to optional userId? and user? interface fields, using the DefaultUser to signal to client-side contexts to use the new vuid identifier.
  • correctly use of the correct React lifecyle methods.

---

Configuration

📅 Schedule: Branch creation - "every weekday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.69%. Comparing base (8939e5b) to head (22ac616).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1200   +/-   ##
=======================================
  Coverage   87.69%   87.69%           
=======================================
  Files         124      124           
  Lines        2299     2299           
  Branches      646      642    -4     
=======================================
  Hits         2016     2016           
  Misses        274      274           
  Partials        9        9           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.