@pouchy_ai/admin-sdk 0.7.0 → 0.7.1

package/CHANGELOG.md

@@ -2,6 +2,24 @@
 
 All notable changes to `@pouchy_ai/admin-sdk` are documented here.
 
+## 0.7.1 — 2026-07-27
+
+Fix: `timeoutMs: 0` now disables the deadline instead of aborting every request.
+
+- **`timeoutMs: 0` means "no deadline".** It previously meant "abort on the next
+  tick": `opts.timeoutMs ?? …` correctly treats `0` as a set value, but that `0`
+  was then handed to `AbortSignal.timeout(0)`, which fires immediately — so a
+  client constructed with `timeoutMs: 0` failed *every* call with the
+  self-contradicting `request timed out after 0ms`. The companion JS SDK has
+  documented `requestTimeoutMs: 0` as "disables" since 0.35.0 and implements it
+  as an explicit `if (!budget)` branch; a host carrying that idiom to this
+  package got the opposite behaviour. The signal is now omitted entirely when
+  the resolved deadline is `0`.
+- No other value changes. An unset `timeoutMs` still resolves to the
+  route-sized default (30s, or `LONG_WORK_TIMEOUT_MS` for the four
+  `maxDuration: 300` handlers), and any positive value still bounds every
+  request as before.
+
 ## 0.7.0 — 2026-07-27
 
 Adds: a throttled request now tells you how long to wait.

package/README.md

@@ -80,6 +80,11 @@ Setting `timeoutMs` explicitly always wins and applies to **every** request, lon
 or short. `requestDeadlineMs(method, path)` returns the default a given request
 would use.
 
+`timeoutMs: 0` **disables** the deadline — the request runs unbounded. This is
+the same contract as the companion JS SDK's `requestTimeoutMs: 0`, so the idiom
+carries between the two packages. (Before 0.7.1 a `0` aborted every request on
+the next tick.)
+
 ## Errors
 
 Every method throws `AdminApiError` on failure — a non-2xx response, a network

package/dist/index.d.ts

@@ -1,4 +1,4 @@
-export declare const ADMIN_SDK_VERSION = "0.7.0";
+export declare const ADMIN_SDK_VERSION = "0.7.1";
 export declare const DEFAULT_BASE_URL = "https://pouchy.ai/v1/admin";
 /** Deadline for the routes whose server handler declares `maxDuration: 300` —
  *  the server's own ceiling plus headroom, so a client abort can only ever mean
@@ -41,7 +41,13 @@ export interface AdminClientOptions {
      *  and the GDPR user delete), which default to
      *  {@link LONG_WORK_TIMEOUT_MS}. Setting this explicitly always wins and
      *  applies to every request, long or short. A request that outlives its
-     *  deadline rejects with an AdminApiError(status 0). */
+     *  deadline rejects with an AdminApiError(status 0).
+     *
+     *  `0` DISABLES the deadline — the request runs unbounded. This mirrors the
+     *  companion JS SDK's `requestTimeoutMs`, whose documented contract is the
+     *  same ("`0` disables"), so the idiom carries between the two packages.
+     *  Before 0.7.1 a `0` here meant "abort on the next tick", i.e. every call
+     *  failed with the self-contradicting `request timed out after 0ms`. */
     timeoutMs?: number;
 }
 /** Thrown on any non-2xx response. `status` is the HTTP status; `message` is the

package/dist/index.js

@@ -8,7 +8,7 @@
 //   import { createAdminClient } from '@pouchy_ai/admin-sdk';
 //   const admin = createAdminClient({ adminKey: process.env.POUCHY_ADMIN_KEY! });
 //   const { agents } = await admin.listAgents();
-export const ADMIN_SDK_VERSION = '0.7.0';
+export const ADMIN_SDK_VERSION = '0.7.1';
 export const DEFAULT_BASE_URL = 'https://pouchy.ai/v1/admin';
 /** Default per-request timeout (ms). A hung upstream otherwise never rejects. */
 const DEFAULT_TIMEOUT_MS = 30_000;
@@ -135,6 +135,8 @@ export function createAdminClient(opts) {
         // An explicit host `timeoutMs` always wins (JS SDK contract); otherwise
         // the deadline is sized to the ROUTE, so the four handlers that declare
         // `maxDuration: 300` are not cut at 30s while they are still working.
+        // `??` (not `||`) is deliberate: 0 is a SET value meaning "no deadline",
+        // and it must not fall through to the route default.
         const timeoutMs = opts.timeoutMs ?? requestDeadlineMs(method, path);
         // Every failure surfaces as an AdminApiError (the doc contract): a
         // network/DNS error or a timeout would otherwise escape as a raw
@@ -149,7 +151,12 @@ export function createAdminClient(opts) {
                     ...(body !== undefined ? { 'content-type': 'application/json' } : {})
                 },
                 body: body !== undefined ? JSON.stringify(body) : undefined,
-                signal: AbortSignal.timeout(timeoutMs)
+                // timeoutMs === 0 → no signal at all. `AbortSignal.timeout(0)`
+                // does NOT mean "no deadline"; it fires on the next tick, so
+                // arming it here aborted every request before the response could
+                // land. The companion JS SDK spells the same branch
+                // (`if (!budget) return this.doFetch(...)`).
+                signal: timeoutMs ? AbortSignal.timeout(timeoutMs) : undefined
             });
         }
         catch (e) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pouchy_ai/admin-sdk",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "description": "Typed TypeScript client for the Pouchy Admin API \u2014 manage agents, keys, end users, knowledge, skills, channels, schedules, webhooks and credentials headlessly, with a project Admin key.",
   "type": "module",
   "license": "SEE LICENSE IN LICENSE",