@rebilly/api 0.10.2 → 0.11.0

package/CHANGELOG.md

@@ -1,3 +1,3 @@
-## 0.10.2 (2026-10-27)
+## 0.11.0 (2026-10-27)
 
 This was a version bump only for rebilly-api to align it with other projects, there were no code changes.

package/dist/core-client.schemas.d.ts

@@ -11075,9 +11075,9 @@ export type OrderReactivation = {
     description?: string | null;
     /**
      * Date and time when the service period starts,
-     * unless the order is canceled but still active.
+     * unless the order is canceled but still active at this time.
      *
-     * If the order is still active,
+     * If the order is still active at this time,
      * the order continues for the current service period.
      *
      * If this field is omitted, this value defaults to the current time.
@@ -11088,8 +11088,8 @@ export type OrderReactivation = {
      * Date and time of the next order renewal.
      * If this field is omitted, this value is computed from the `effectiveTime` field.
      *
-     * If the order is canceled but still active,
-     * it is ignored and the next renewal occurs as scheduled.
+     * If the order is canceled but still active at the `effectiveTime`,
+     * this field is ignored and the next renewal occurs as scheduled.
      * @format date-time
      */
     renewalTime?: string;
@@ -11454,9 +11454,9 @@ export type SubscriptionReactivation = {
     description?: string | null;
     /**
      * Date and time when the service period starts,
-     * unless the subscription is canceled but still active.
+     * unless the subscription is canceled but still active at this time.
      *
-     * If the subscription is still active,
+     * If the subscription is still active at this time,
      * the subscription continues for the current service period.
      *
      * If this field is omitted, this value defaults to the current time.
@@ -11467,8 +11467,8 @@ export type SubscriptionReactivation = {
      * Date and time of the next subscription renewal.
      * If this field is omitted, this value is computed from the `effectiveTime` field.
      *
-     * If the subscription is canceled but still active,
-     * it is ignored and the next renewal occurs as scheduled.
+     * If the subscription is canceled but still active at the `effectiveTime`,
+     * this field is ignored and the next renewal occurs as scheduled.
      * @format date-time
      */
     renewalTime?: string;
@@ -13357,7 +13357,7 @@ export type PayoutRequestTimelineMessage = {
     /**
      * Type of timeline event.
      */
-    readonly type: "timeline-comment-created" | "payout-request-created" | "payout-request-ready" | "payout-request-returned-to-pending" | "payout-request-approved" | "payout-request-approval-undone" | "payout-request-allocated" | "payout-request-processing-started" | "payout-request-fulfilled" | "payout-request-canceled" | "payout-request-reversed" | "payout-request-blocked" | "payout-request-unblocked" | "payout-request-added-to-batch" | "payout-request-removed-from-batch";
+    readonly type: "timeline-comment-created" | "payout-request-created" | "payout-request-ready" | "payout-request-returned-to-pending" | "payout-request-approved" | "payout-request-approval-undone" | "payout-request-allocated" | "payout-request-processing-started" | "payout-request-fulfilled" | "payout-request-canceled" | "payout-request-reversed" | "payout-request-blocked" | "payout-request-unblocked" | "payout-request-added-to-batch" | "payout-request-removed-from-batch" | "payout-request-auto-allocation-failed";
     /**
      * Date and time when the timeline event occurred.
      */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rebilly/api",
-  "version": "0.10.2",
+  "version": "0.11.0",
   "description": "Rebilly Core and Storefront API clients generated from the OpenAPI definitions",
   "type": "module",
   "sideEffects": false,