@lockerverse/react 0.2.185 → 0.2.190-dev.1

package/MIGRATIONS.md

@@ -36,6 +36,19 @@ If it cannot be found, report that limit and use the baseline review below. Do n
 claim that every historical migration was applied. Read this file even if the
 version already matches: a previous upgrade may have missed host adoption steps.
 
+## 0.2.190-dev.1 — widget load recovery and Sentry releases
+
+- **Affected:** Core widget loading and SDK failure reporting.
+- **Automatic:** a widget GET retries once after a network failure or request
+  timeout, with a full timeout for each attempt. Invalid responses, cancellation,
+  HTTP errors, and payment submissions do not retry. Only the final failure is
+  reported. Errors expose the safe optional `failureKind` field; Sentry receives
+  `sdk.failure_kind` and a valid `lockerverse-sdk@<version>` release name.
+- **Required host changes:** upgrade Core and React together and deploy the host.
+  No integration code changes are required.
+- **Check:** interrupt the first widget request and confirm that the second loads
+  the widget. Check the final failure classification and Sentry release association.
+
 ## 0.2.185 — shipping for additional items
 
 - **Affected:** Core checkout estimates and the React donation launcher.
@@ -50,6 +63,7 @@ version already matches: a previous upgrade may have missed host adoption steps.
 - **Check:** select one, two, and the maximum allowed trigger quantity. Confirm the
   local summary and server quote agree; removing all trigger items removes shipping.
 
+
 ## 0.2.184 — single focus boundary for form fields
 
 - **Affected:** React form controls and the shared phone field in payment and signup.
@@ -69,7 +83,7 @@ Widgets can now use a private contact list for email eligibility, a fixed amount
 Required shipping appears in `catalog.widget.requiredShipping`. Do not offer this product as a separate shopper choice. The SDK adds its quantity once when a trigger product is selected; the server also enforces this rule. Render authoritative quote line items and totals, including shipping. The built-in launcher and payment summary handle this automatically.
 
 
-## 0.2.177 — Secure checkout loading recovery
+## 0.2.176-dev.1 — Secure checkout loading recovery
 
 - **Affected:** React payment widget Stripe fields.
 - **Automatic:** failed field or script loads show a reload action. Fields that
@@ -81,9 +95,23 @@ Required shipping appears in `catalog.widget.requiredShipping`. Do not offer thi
 - Reload is an explicit customer action and can clear unsaved form entries.
   Saved payment recovery remains in session storage.
 
-
 ## 0.2.175 — Match Stripe Elements payment method configuration
 
+- **Affected:** Core checkout submission and React payment widgets.
+- **Automatic:** React configures explicit card, Link, and community-enabled bank
+  methods in Stripe Elements and marks the confirmation request with
+  `paymentMethodConfiguration: "explicit"`. This matches the backend's Stripe
+  PaymentIntent configuration.
+- **Required:** deploy the backend that supports this optional marker before
+  upgrading React. Keep Core and React matched. Existing Core-only callers omit
+  the marker and retain automatic payment methods. Custom Elements integrations
+  must send the marker only when they use the explicit method list.
+- **Check:** submit card and bank payments through Stripe Elements in test mode,
+  including recurring checkout. Confirm pending recovery and settlement.
+
+
+## 0.2.174-dev.1 — Match Stripe Elements payment method configuration
+
 - **Affected:** Core checkout submission and React payment widgets.
 - **Automatic:** React configures explicit card, Link, and community-enabled bank
   methods in Stripe Elements and marks the confirmation request with
@@ -157,7 +185,39 @@ Required shipping appears in `catalog.widget.requiredShipping`. Do not offer thi
   verify a changed selection cannot discard it. Check both paid and free order
   confirmation panels. Do not submit a live transaction for this check.
 
-## 0.2.170 — six-month payment widgets
+## 0.2.172-dev.1 — Check pending payment status
+
+- **Affected:** React payment widgets with unresolved payments.
+- **Automatic behavior:** the existing pending-payment screen now offers Check
+  payment status. It checks the saved payment reference and cannot submit a new
+  payment. The control is disabled while the check runs.
+- **Required host changes:** none. Update Core and React together.
+- **Verification:** complete a test bank payment, return to its pending checkout,
+  and check its status. Confirm completion clears recovery storage.
+
+## 0.2.171-dev.1 — SDK payment recovery and completion UI
+
+- **Affected:** React payment widgets and custom hosts that persist payment recovery.
+- **Optional adoption:** pass `recoveryStorageKey` to `LockerversePayment` to let
+  the SDK save and restore the pending payment in session storage. Use a stable
+  key scoped to the API environment, community, and widget. Remove the host's
+  storage code and recovery-driven component key. Do not combine automatic
+  persistence with a second host persistence writer.
+- **Compatibility:** the SDK reads the hosted Next app's existing version 1
+  records when the same key is used. It writes version 2 records with widget
+  identity. It checks widget and selection identity before recovery and keeps
+  an unresolved record if those details differ. Recovery uses the saved connected
+  account even if current payment routing has changed. Storage is read after hydration,
+  before the payable form mounts. No contact details or payment tokens are saved.
+- **Optional UI adoption:** use `completionView="summary"` for the SDK confirmation
+  panel and remove the host's duplicate success panel. Completion callbacks still
+  run. The default inline message and explicit `resumePayment` integrations remain
+  supported. Auctions and legacy custom checkout forms are unchanged.
+- **Check:** reload a pending checkout and confirm the existing payment is checked;
+  verify a changed selection cannot discard it. Check both paid and free order
+  confirmation panels. Do not submit a live transaction for this check.
+
+## 0.2.169-dev.1 — six-month payment widgets
 
 Affected: @lockerverse/sdk checkout and @lockerverse/react payment widgets.
 
@@ -173,6 +233,31 @@ Affected: @lockerverse/sdk checkout and @lockerverse/react payment widgets.
   submission. Do not submit a live payment for an integration check.
 
 
+## 0.2.168-dev.1 — bank authorization terms
+
+- **Affected:** React payment widgets with ACH enabled.
+- **Automatic:** Stripe displays its bank authorization terms before payment confirmation.
+- **Adoption:** update the matching SDK/React development pair. No prop changes are required.
+- **Check:** confirm that the bank authorization text is visible when a bank account is selected.
+
+## 0.2.167-dev.1 — widget ACH and subscription payment recovery
+
+- **Affected:** Core checkout data and React payment widgets.
+- **Automatic:** bank payment availability follows the organization default and
+  community override returned by the backend. Missing policy remains disabled.
+  Pending payments keep their existing payment reference. A failed subscription
+  invoice can return `action_required` with `requiresAction: false` and `retryUrl`;
+  React shows a link to pay the same invoice instead of creating a second subscription.
+- **Required for custom payment UI:** preserve the reference for pending and
+  action-required results. Handle `retryUrl` by opening that invoice, and recover
+  status before permitting a new checkout. Do not treat submission as settlement.
+- **Adoption:** deploy the matching backend policy and recovery contract before
+  enabling ACH. Existing React hosts need no component prop changes. Keep Core and
+  React versions matched when upgrading. Auction payment methods are unchanged.
+- **Check:** verify disabled/inherited/enabled bank visibility and pending, bank
+  verification, invoice retry, success, and terminal failure in Stripe test mode.
+  Do not create a live transaction for this check.
+
 ## 0.2.166 — single dropdown arrow
 
 - **Affected:** native single-select custom fields in React signup and payment forms.

package/guides/auctions.md

@@ -1,6 +1,6 @@
 # Lockerverse auctions guide
 
-Package: @lockerverse/react@0.2.185
+Package: @lockerverse/react@0.2.190-dev.1
 
 Generated from this release's maintained documentation. Do not edit this copy.
 

package/guides/events.md

@@ -1,6 +1,6 @@
 # Lockerverse events guide
 
-Package: @lockerverse/react@0.2.185
+Package: @lockerverse/react@0.2.190-dev.1
 
 Generated from this release's maintained documentation. Do not edit this copy.
 

package/guides/integration.md

@@ -1,6 +1,6 @@
 # Lockerverse integration guide
 
-Package: @lockerverse/react@0.2.185
+Package: @lockerverse/react@0.2.190-dev.1
 
 Generated from this release's maintained documentation. Do not edit this copy.
 

package/guides/payment-widgets.md

@@ -1,6 +1,6 @@
 # Lockerverse payment-widgets guide
 
-Package: @lockerverse/react@0.2.185
+Package: @lockerverse/react@0.2.190-dev.1
 
 Generated from this release's maintained documentation. Do not edit this copy.
 

package/guides/signup.md

@@ -1,6 +1,6 @@
 # Lockerverse signup guide
 
-Package: @lockerverse/react@0.2.185
+Package: @lockerverse/react@0.2.190-dev.1
 
 Generated from this release's maintained documentation. Do not edit this copy.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lockerverse/react",
-  "version": "0.2.185",
+  "version": "0.2.190-dev.1",
   "description": "Tree-shakable React payment and signup UI for Lockerverse",
   "repository": {
     "type": "git",
@@ -136,7 +136,7 @@
     "embla-carousel-react": "8.6.0",
     "lucide-react": "0.536.0",
     "valibot": "1.4.2",
-    "@lockerverse/sdk": "0.2.185"
+    "@lockerverse/sdk": "0.2.190-dev.1"
   },
   "devDependencies": {
     "@size-limit/file": "13.0.3",