@v-office/website-sdk 2.16.2 → 2.16.3

package/dist/cli.mjs

@@ -16,7 +16,7 @@ var CLICheckFailed = class extends Error {
 const toCLIError = (message, cause) => cause instanceof Error ? new CLICheckFailed(`${message}: ${cause.message}`, { cause }) : new CLICheckFailed(message, { cause });
 //#endregion
 //#region package.json
-var version = "2.16.2";
+var version = "2.16.3";
 //#endregion
 //#region src/cli/output.ts
 const toJson = (value) => Effect.try({

package/dist/instructions/CHANGELOG.md

@@ -4,6 +4,7 @@ This file is the versioned changelog index for the website SDK instructions.
 
 ## Versions
 
+- `versions/2.16.3/CHANGELOG.md`: `@v-office/website-sdk` 2.16.3 release notes.
 - `versions/2.16.2/CHANGELOG.md`: `@v-office/website-sdk` 2.16.2 documentation release notes.
 - `versions/2.16.1/CHANGELOG.md`: `@v-office/website-sdk` 2.16.1 release notes.
 - `versions/2.16.0/CHANGELOG.md`: `@v-office/website-sdk` 2.16.0 release notes.

package/dist/instructions/MIGRATION.md

@@ -4,6 +4,7 @@ This file is the versioned migration index for the website SDK instructions.
 
 ## Available Guides
 
+- `versions/2.16.3/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.2 to 2.16.3.
 - `versions/2.16.2/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.1 to 2.16.2.
 - `versions/2.16.1/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.0 to 2.16.1.
 - `versions/2.16.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.15.0 to 2.16.0.

package/dist/instructions/README.md

@@ -1,7 +1,7 @@
 # Website SDK Instructions
 
 These instructions describe the current source targeted for
-`@v-office/website-sdk` 2.16.2. Package versions remain unchanged until the release
+`@v-office/website-sdk` 2.16.3. Package versions remain unchanged until the release
 workflow performs the coordinated core and website bumps.
 
 Use this directory as the consumer-facing reference for the package:
@@ -18,6 +18,8 @@ Use this directory as the consumer-facing reference for the package:
 - `document-structured-json.md`: `sdk.static.documents.getTermsAndPrivacyPolicy` and structured document JSON rendering rules.
 - `CHANGELOG.md`: versioned changelog index.
 - `MIGRATION.md`: versioned migration index.
+- `versions/2.16.3/`: 2.16.3 browser-origin resolution for relative payment
+  return URLs and the 2.16.2-to-2.16.3 migration guide.
 - `versions/2.16.2/`: 2.16.2 documentation release notes and migration guide.
 - `versions/2.16.1/`: 2.16.1 v10 multi-rate resolution restricted to rent rates,
   restored additional-service availability, and the 2.16.0-to-2.16.1 migration

package/dist/instructions/booking.md

@@ -68,6 +68,10 @@ const booking = await sdk.live.booking.book({
 `kind: "OPTION"` creates an option booking on v10 and legacy v9. Omitting `kind`,
 or passing `"CONFIRMED"`, retains the existing confirmed-booking behavior.
 `relativeRedirectUrl` is used for online payment redirects after booking creation.
+In a browser, the SDK resolves a relative value against `window.location.origin`
+before initializing a v10 Adyen payment. An absolute HTTP or HTTPS URL is passed
+through unchanged. Server-side callers must provide an absolute HTTP or HTTPS URL
+because no browser origin is available.
 
 ## Output
 
@@ -167,7 +171,13 @@ try {
 
 ## Payment Return
 
-Online payment providers return the guest to a URL derived from `relativeRedirectUrl`. Stripe returns to that path with `payment=stripe&success=true` after payment and `payment=stripe&cancel=true` after cancellation, so the path must exist in your site and should read those query parameters.
+Online payment providers return the guest to a URL derived from
+`relativeRedirectUrl`. A relative value such as `/booking/payment-return` uses
+the active browser origin, including `http://localhost:<port>` during local
+development and the deployed website origin in production. Stripe returns to
+that path with `payment=stripe&success=true` after payment and
+`payment=stripe&cancel=true` after cancellation, so the path must exist in your
+site and should read those query parameters.
 
 `relativeRedirectUrl` is supplied before the reservation exists, so the return URL cannot carry the booking number. Persist whatever the return page needs, for example in `sessionStorage`, before submitting a payment option.
 

package/dist/instructions/versions/2.16.3/CHANGELOG.md

@@ -0,0 +1,31 @@
+# Changelog: 2.16.3
+
+This release fixes v10 Adyen payment return URLs when booking is initiated with
+a relative `relativeRedirectUrl`.
+
+## Fixed
+
+- Relative payment return URLs are resolved against `window.location.origin`
+  before the SDK initializes an Adyen payment.
+- Adyen receives the website's complete return URL instead of an unresolved
+  path that could be interpreted relative to the payment provider's origin.
+- Local development can initialize test payments with return URLs such as
+  `http://localhost:4321/booking/payment-return`.
+
+## Unchanged
+
+- `sdk.live.booking.book`, its input, and its output keep the same public types.
+- Existing relative values such as `/booking/payment-return` require no code
+  changes.
+- Absolute HTTP and HTTPS return URLs continue to be passed through unchanged.
+- Legacy v9 booking and payment behavior is unchanged.
+
+## Compatibility
+
+- No consumer code change is required. Upgrade the website SDK and refresh the
+  lockfile.
+- Browser callers can keep supplying a site-relative return path. Server-side
+  callers must supply an absolute HTTP or HTTPS URL because no browser origin is
+  available.
+
+See `versions/2.16.3/MIGRATION.md` and `../../booking.md`.

package/dist/instructions/versions/2.16.3/MIGRATION.md

@@ -0,0 +1,51 @@
+# Migration: 2.16.2 to 2.16.3
+
+2.16.3 fixes relative v10 Adyen payment return URLs through
+`@v-office/sdk-core` 1.16.2. No public type, service call, input, or result shape
+changes.
+
+## 1. Upgrade
+
+```sh
+pnpm add @v-office/website-sdk@2.16.3
+```
+
+Refresh the lockfile so the website SDK resolves `@v-office/sdk-core` 1.16.2.
+
+## 2. Keep the Existing Return Path
+
+No application code change is required. Existing relative return paths continue
+to work:
+
+```ts
+const booking = await sdk.live.booking.book({
+  quote,
+  contact,
+  relativeRedirectUrl: "/booking/payment-return",
+});
+```
+
+In a browser, the SDK now resolves that path against `window.location.origin`.
+For example:
+
+```text
+http://localhost:4321 + /booking/payment-return
+→ http://localhost:4321/booking/payment-return
+```
+
+Absolute HTTP and HTTPS return URLs remain unchanged. Server-side callers must
+provide an absolute URL because `window.location.origin` is unavailable.
+
+## Required Consumer Work
+
+None beyond upgrading the dependency and refreshing the lockfile.
+
+## Recommended Verification
+
+1. Start the website locally and create a deliberate v10 test booking.
+2. Confirm the Adyen initiation request contains the local website origin in its
+   `redirectUrl`.
+3. Complete or cancel the hosted test payment and confirm the browser returns to
+   the local payment-return page.
+4. Confirm a deployed website uses its own active origin for the same relative
+   return path.

package/instructions/CHANGELOG.md

@@ -4,6 +4,7 @@ This file is the versioned changelog index for the website SDK instructions.
 
 ## Versions
 
+- `versions/2.16.3/CHANGELOG.md`: `@v-office/website-sdk` 2.16.3 release notes.
 - `versions/2.16.2/CHANGELOG.md`: `@v-office/website-sdk` 2.16.2 documentation release notes.
 - `versions/2.16.1/CHANGELOG.md`: `@v-office/website-sdk` 2.16.1 release notes.
 - `versions/2.16.0/CHANGELOG.md`: `@v-office/website-sdk` 2.16.0 release notes.

package/instructions/MIGRATION.md

@@ -4,6 +4,7 @@ This file is the versioned migration index for the website SDK instructions.
 
 ## Available Guides
 
+- `versions/2.16.3/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.2 to 2.16.3.
 - `versions/2.16.2/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.1 to 2.16.2.
 - `versions/2.16.1/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.0 to 2.16.1.
 - `versions/2.16.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.15.0 to 2.16.0.

package/instructions/README.md

@@ -1,7 +1,7 @@
 # Website SDK Instructions
 
 These instructions describe the current source targeted for
-`@v-office/website-sdk` 2.16.2. Package versions remain unchanged until the release
+`@v-office/website-sdk` 2.16.3. Package versions remain unchanged until the release
 workflow performs the coordinated core and website bumps.
 
 Use this directory as the consumer-facing reference for the package:
@@ -18,6 +18,8 @@ Use this directory as the consumer-facing reference for the package:
 - `document-structured-json.md`: `sdk.static.documents.getTermsAndPrivacyPolicy` and structured document JSON rendering rules.
 - `CHANGELOG.md`: versioned changelog index.
 - `MIGRATION.md`: versioned migration index.
+- `versions/2.16.3/`: 2.16.3 browser-origin resolution for relative payment
+  return URLs and the 2.16.2-to-2.16.3 migration guide.
 - `versions/2.16.2/`: 2.16.2 documentation release notes and migration guide.
 - `versions/2.16.1/`: 2.16.1 v10 multi-rate resolution restricted to rent rates,
   restored additional-service availability, and the 2.16.0-to-2.16.1 migration

package/instructions/booking.md

@@ -68,6 +68,10 @@ const booking = await sdk.live.booking.book({
 `kind: "OPTION"` creates an option booking on v10 and legacy v9. Omitting `kind`,
 or passing `"CONFIRMED"`, retains the existing confirmed-booking behavior.
 `relativeRedirectUrl` is used for online payment redirects after booking creation.
+In a browser, the SDK resolves a relative value against `window.location.origin`
+before initializing a v10 Adyen payment. An absolute HTTP or HTTPS URL is passed
+through unchanged. Server-side callers must provide an absolute HTTP or HTTPS URL
+because no browser origin is available.
 
 ## Output
 
@@ -167,7 +171,13 @@ try {
 
 ## Payment Return
 
-Online payment providers return the guest to a URL derived from `relativeRedirectUrl`. Stripe returns to that path with `payment=stripe&success=true` after payment and `payment=stripe&cancel=true` after cancellation, so the path must exist in your site and should read those query parameters.
+Online payment providers return the guest to a URL derived from
+`relativeRedirectUrl`. A relative value such as `/booking/payment-return` uses
+the active browser origin, including `http://localhost:<port>` during local
+development and the deployed website origin in production. Stripe returns to
+that path with `payment=stripe&success=true` after payment and
+`payment=stripe&cancel=true` after cancellation, so the path must exist in your
+site and should read those query parameters.
 
 `relativeRedirectUrl` is supplied before the reservation exists, so the return URL cannot carry the booking number. Persist whatever the return page needs, for example in `sessionStorage`, before submitting a payment option.
 

package/instructions/versions/2.16.3/CHANGELOG.md

@@ -0,0 +1,31 @@
+# Changelog: 2.16.3
+
+This release fixes v10 Adyen payment return URLs when booking is initiated with
+a relative `relativeRedirectUrl`.
+
+## Fixed
+
+- Relative payment return URLs are resolved against `window.location.origin`
+  before the SDK initializes an Adyen payment.
+- Adyen receives the website's complete return URL instead of an unresolved
+  path that could be interpreted relative to the payment provider's origin.
+- Local development can initialize test payments with return URLs such as
+  `http://localhost:4321/booking/payment-return`.
+
+## Unchanged
+
+- `sdk.live.booking.book`, its input, and its output keep the same public types.
+- Existing relative values such as `/booking/payment-return` require no code
+  changes.
+- Absolute HTTP and HTTPS return URLs continue to be passed through unchanged.
+- Legacy v9 booking and payment behavior is unchanged.
+
+## Compatibility
+
+- No consumer code change is required. Upgrade the website SDK and refresh the
+  lockfile.
+- Browser callers can keep supplying a site-relative return path. Server-side
+  callers must supply an absolute HTTP or HTTPS URL because no browser origin is
+  available.
+
+See `versions/2.16.3/MIGRATION.md` and `../../booking.md`.

package/instructions/versions/2.16.3/MIGRATION.md

@@ -0,0 +1,51 @@
+# Migration: 2.16.2 to 2.16.3
+
+2.16.3 fixes relative v10 Adyen payment return URLs through
+`@v-office/sdk-core` 1.16.2. No public type, service call, input, or result shape
+changes.
+
+## 1. Upgrade
+
+```sh
+pnpm add @v-office/website-sdk@2.16.3
+```
+
+Refresh the lockfile so the website SDK resolves `@v-office/sdk-core` 1.16.2.
+
+## 2. Keep the Existing Return Path
+
+No application code change is required. Existing relative return paths continue
+to work:
+
+```ts
+const booking = await sdk.live.booking.book({
+  quote,
+  contact,
+  relativeRedirectUrl: "/booking/payment-return",
+});
+```
+
+In a browser, the SDK now resolves that path against `window.location.origin`.
+For example:
+
+```text
+http://localhost:4321 + /booking/payment-return
+→ http://localhost:4321/booking/payment-return
+```
+
+Absolute HTTP and HTTPS return URLs remain unchanged. Server-side callers must
+provide an absolute URL because `window.location.origin` is unavailable.
+
+## Required Consumer Work
+
+None beyond upgrading the dependency and refreshing the lockfile.
+
+## Recommended Verification
+
+1. Start the website locally and create a deliberate v10 test booking.
+2. Confirm the Adyen initiation request contains the local website origin in its
+   `redirectUrl`.
+3. Complete or cancel the hosted test payment and confirm the browser returns to
+   the local payment-return page.
+4. Confirm a deployed website uses its own active origin for the same relative
+   return path.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@v-office/website-sdk",
-  "version": "2.16.2",
+  "version": "2.16.3",
   "description": "Website-facing SDK facade backed by @v-office/sdk-core",
   "bin": {
     "website-sdk": "./dist/cli.mjs"
@@ -42,7 +42,7 @@
   },
   "dependencies": {
     "@graphql-typed-document-node/core": "3.2.0",
-    "@v-office/sdk-core": "^1.16.1",
+    "@v-office/sdk-core": "^1.16.2",
     "effect": "4.0.0-beta.85",
     "graphql": "17.0.2",
     "yaml": "^2.9.0"