tf-checkout-react 2.0.0-beta.24 → 2.0.0-beta.25

package/README.md

@@ -7,16 +7,16 @@ components, plus the shared API and React Query hooks. Which paths a buyer can
 actually use depend on the event, the deployed API, the buyer's session and the
 payment provider.
 
-This reference describes **2.0.0-beta.24**. It is a prerelease with a different
+This reference describes **2.0.0-beta.25**. It is a prerelease with a different
 API from 1.x. Pin the version while evaluating it. npm's `latest` and `beta`
 tags can move independently and an unqualified install may select 1.x:
 
 ```bash
 npm view tf-checkout-react dist-tags
-npm install tf-checkout-react@2.0.0-beta.24 @tanstack/react-query react react-dom
+npm install tf-checkout-react@2.0.0-beta.25 @tanstack/react-query react react-dom
 ```
 
-The [API reference](https://unpkg.com/tf-checkout-react@2.0.0-beta.24/docs/API.md)
+The [API reference](https://unpkg.com/tf-checkout-react@2.0.0-beta.25/docs/API.md)
 is included as `docs/API.md` in this package.
 
 Contents: [Requirements](#requirements) · [Quick start](#quick-start) ·
@@ -354,7 +354,7 @@ holder's answers in `ticketDataCapture`, and add-on answers via
 the opaque catalog ID. Use backend country/state IDs for `countryId` and
 `stateId`; `countryCode` / `stateCode` are payment billing codes.
 
-In beta.24 conditional custom-field requiredness is left to the backend and
+In beta.25 conditional custom-field requiredness is left to the backend and
 not all hosted-checkout conditional visibility is reproduced. Verify the
 actual event against the deployed checkout, including blanks, images, holder
 scoping and validation errors; do not claim parity from the presence of a
@@ -366,7 +366,7 @@ Failed waiver reads other than a 404 remain unknown and block placement; use
 `reloadCheckoutDetails()` to retry rather than silently skipping it.
 `WaiverSigning` handles the SDK's signing flow.
 
-**Consent limitation in beta.24:** when `privacyPolicy` is supplied, the
+**Consent limitation in beta.25:** when `privacyPolicy` is supplied, the
 stock `BillingInfo` replaces the Ticket Fairy marketing checkbox with the
 required privacy checkbox, but both use `consent.ttfOptIn`; the order sends
 that value as `ttf_opt_in`. The privacy acknowledgement and Ticket Fairy
@@ -819,7 +819,7 @@ existing 1.x integration pinned until the new flow and backend are verified.
 There is no automatic translation of old URLs, component props, account
 sessions or persisted 1.x state.
 
-| 1.x integration | 2.0.0-beta.24 approach |
+| 1.x integration | 2.0.0-beta.25 approach |
 | --- | --- |
 | `setConfigs({ BASE_URL, ... })` | `configureCheckout({ env` or `baseUrl`, `clientId`, `clientSecret: ''`, ... `})`; public client registration and session setup are required. |
 | `TicketsContainer`, `SeatMapContainer`, `AddOnsContainer` | `EmbeddedCheckout` or `Tickets`, `SeatMap`, `AddOns` under `CheckoutProvider`. Adapt callbacks and navigation. |

package/docs/API.md

@@ -1,7 +1,7 @@
 # React checkout API reference
 
 This reference describes the public surface of `tf-checkout-react` version
-`2.0.0-beta.24`. It supplements the package's npm README with examples and an
+`2.0.0-beta.25`. It supplements the package's npm README with examples and an
 inventory of the shared facade and hooks. The package's installed
 `dist/index.d.ts` is the exact versioned source for complete signatures and
 DTO fields. A named export or a typed payment method does not establish that

package/package.json

@@ -1,5 +1,5 @@
 {
-  "version": "2.0.0-beta.24",
+  "version": "2.0.0-beta.25",
   "license": "MIT",
   "main": "dist/index.js",
   "typings": "dist/index.d.ts",