@vxil/sdk 0.26.1 → 0.26.2
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/dist/index.d.ts +5 -1
- package/dist/retry.d.ts +5 -2
- package/dist/retry.js +6 -3
- package/package.json +1 -1
package/dist/index.d.ts
CHANGED
|
@@ -1727,7 +1727,11 @@ export interface PaymentsSubscriptionGrantedEventPayload {
|
|
|
1727
1727
|
state: 'ok';
|
|
1728
1728
|
}
|
|
1729
1729
|
/** `payments.subscription.revoked` — a row ended by `/revoke` or `DELETE`, or by
|
|
1730
|
-
* its charge's full refund / chargeback
|
|
1730
|
+
* its charge's full refund / chargeback: a charge-linked grant or pass, or
|
|
1731
|
+
* (since 2026-10-13) a provider subscription (Stripe, Paddle, PayPal,
|
|
1732
|
+
* RevenueCat) whose current period's charge was fully refunded or disputed.
|
|
1733
|
+
* `charge_id` is null when the money-back names no recorded charge
|
|
1734
|
+
* (RevenueCat). */
|
|
1731
1735
|
export interface PaymentsSubscriptionRevokedEventPayload {
|
|
1732
1736
|
end_user_id: string;
|
|
1733
1737
|
subscription_id: string;
|
package/dist/retry.d.ts
CHANGED
|
@@ -53,7 +53,10 @@ export declare const CAPACITY_ERROR_CODES: ReadonlySet<string>;
|
|
|
53
53
|
/** The 503 answers retried the same way (M1, 2026-10-04): the generation
|
|
54
54
|
* lane could not reach payments to place its credit hold — nothing was
|
|
55
55
|
* started and nothing held, and the SAME request re-sent after Retry-After
|
|
56
|
-
* starts the run (the refused run released its idempotency key).
|
|
56
|
+
* starts the run (the refused run released its idempotency key).
|
|
57
|
+
* `outcome_unknown` (JOBS-ENQUEUE-500-AFTER-COMMIT, 2026-10-13): the run was
|
|
58
|
+
* committed but its enqueue could not be confirmed — the SAME keyed request
|
|
59
|
+
* re-sent answers with that run (`retryOnCapacity` always sends a key). */
|
|
57
60
|
export declare const UNAVAILABLE_ERROR_CODES: ReadonlySet<string>;
|
|
58
61
|
/** The 409 answers retried the same way: the run this idempotency_key names
|
|
59
62
|
* is still placing its credit hold (`generation_in_progress`, Retry-After 5)
|
|
@@ -74,7 +77,7 @@ export interface RetryOnCapacityOptions {
|
|
|
74
77
|
}
|
|
75
78
|
/**
|
|
76
79
|
* Re-run `attempt` while it throws a CAPACITY 429 (`CAPACITY_ERROR_CODES`),
|
|
77
|
-
* a 503 `payments_unavailable` / `enqueue_interrupted` (`UNAVAILABLE_ERROR_CODES`)
|
|
80
|
+
* a 503 `payments_unavailable` / `enqueue_interrupted` / `outcome_unknown` (`UNAVAILABLE_ERROR_CODES`)
|
|
78
81
|
* or a 409 `generation_in_progress` (`IN_PROGRESS_ERROR_CODES`):
|
|
79
82
|
* wait the server's `Retry-After` (else 5 s) plus up to 20 % jitter (≤ 1 s,
|
|
80
83
|
* so many clients told the same second do not all return on it), and never
|
package/dist/retry.js
CHANGED
|
@@ -165,8 +165,11 @@ export const CAPACITY_ERROR_CODES = new Set([
|
|
|
165
165
|
/** The 503 answers retried the same way (M1, 2026-10-04): the generation
|
|
166
166
|
* lane could not reach payments to place its credit hold — nothing was
|
|
167
167
|
* started and nothing held, and the SAME request re-sent after Retry-After
|
|
168
|
-
* starts the run (the refused run released its idempotency key).
|
|
169
|
-
|
|
168
|
+
* starts the run (the refused run released its idempotency key).
|
|
169
|
+
* `outcome_unknown` (JOBS-ENQUEUE-500-AFTER-COMMIT, 2026-10-13): the run was
|
|
170
|
+
* committed but its enqueue could not be confirmed — the SAME keyed request
|
|
171
|
+
* re-sent answers with that run (`retryOnCapacity` always sends a key). */
|
|
172
|
+
export const UNAVAILABLE_ERROR_CODES = new Set(['payments_unavailable', 'enqueue_interrupted', 'outcome_unknown']);
|
|
170
173
|
/** The 409 answers retried the same way: the run this idempotency_key names
|
|
171
174
|
* is still placing its credit hold (`generation_in_progress`, Retry-After 5)
|
|
172
175
|
* — the SAME request re-sent then answers with that run (or, when the
|
|
@@ -186,7 +189,7 @@ export function isCapacityRetryable(e) {
|
|
|
186
189
|
const CAPACITY_DEFAULT_WAIT_MS = 5_000;
|
|
187
190
|
/**
|
|
188
191
|
* Re-run `attempt` while it throws a CAPACITY 429 (`CAPACITY_ERROR_CODES`),
|
|
189
|
-
* a 503 `payments_unavailable` / `enqueue_interrupted` (`UNAVAILABLE_ERROR_CODES`)
|
|
192
|
+
* a 503 `payments_unavailable` / `enqueue_interrupted` / `outcome_unknown` (`UNAVAILABLE_ERROR_CODES`)
|
|
190
193
|
* or a 409 `generation_in_progress` (`IN_PROGRESS_ERROR_CODES`):
|
|
191
194
|
* wait the server's `Retry-After` (else 5 s) plus up to 20 % jitter (≤ 1 s,
|
|
192
195
|
* so many clients told the same second do not all return on it), and never
|
package/package.json
CHANGED