@returningai/widget-sdk 1.4.3 → 1.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -7,6 +7,32 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ---
9
9
 
10
+ ## [1.5.0] — 2026-06-03
11
+
12
+ ### Added
13
+
14
+ - Store and custom-store widgets can now register a host callback named
15
+ `callbackFieldOptions` to populate callback-backed purchase fields from the
16
+ customer's backend.
17
+ - Added per-widget callback registration APIs:
18
+ `widget.registerCallback(callbackName, callback)` and
19
+ `widget.lockCallbacks()`. Register callbacks on the specific widget element
20
+ so pages with multiple widgets can route each widget to its own handler.
21
+ - Added TypeScript exports for the store callback payload and result types,
22
+ including `StoreCallbackFieldOptionsPayload`,
23
+ `StoreCallbackFieldOptionsResult`, and
24
+ `ReturningAIStoreCallbackFieldOptionsCallback`.
25
+
26
+ ### Changed
27
+
28
+ - Store callback examples now call the customer's backend from the browser
29
+ callback and expect the backend to return `{ fieldOptions, signature }`.
30
+ Keep SDK access credentials on the backend; do not call ReturningAI's
31
+ callback-signature endpoint from browser code.
32
+ - Callback registration now supports both iframe mode and bundle mode.
33
+
34
+ ---
35
+
10
36
  ## [Security Notice — 2026-05-11] Refresh-token TTL change for Access Key Embed
11
37
 
12
38
  **This is a server-side change. No SDK code update is required. Customers do