@pipelex/sdk 0.28.1 → 0.29.1

package/README.md

@@ -126,7 +126,7 @@ The full client surface is documented in [`docs/architecture.md`](./docs/archite
 
 ## Documentation
 
-These pages ship inside the published package, so a reader who has only installed it opens them under `node_modules/@pipelex/sdk/docs/` — at the version being called, rather than whatever the repository's default branch says today. They are also browsable at [`Pipelex/pipelex-sdk-js/tree/main/docs`](https://github.com/Pipelex/pipelex-sdk-js/tree/main/docs), which is the address to give someone who has not installed the package.
+These pages ship inside the published package, so a reader who has only installed it opens them under `node_modules/@pipelex/sdk/docs/` — at the version being called, rather than whatever the repository's default branch says today. They are also browsable at [`Pipelex/pipelex-sdk/tree/main/js/docs`](https://github.com/Pipelex/pipelex-sdk/tree/main/js/docs), which is the address to give someone who has not installed the package.
 
 | Page | What it covers |
 | --- | --- |

package/dist/client.d.ts

@@ -347,7 +347,7 @@ export declare class PipelexApiClient implements MTHDSProtocol<DictPipeOutput> {
      *    other extension route rides the static core (`crate_ops.py` is explicit that
      *    `build/runner` "is the exception — it needs the dry-run sweep"). Giving one
      *    static route an override while its siblings lack one is the inconsistency.
-     * 2. The input is **bounded server-side** — `pipelex-api/api/limits.py` caps a request
+     * 2. The input is **bounded server-side** — the runner's `pipelex_api/limits.py` caps a request
      *    at 16 `.mthds` files of 1 MiB each — and none of these routes runs inference.
      * 3. On the hosted path an override would be **inert**: the gateway caps responses at
      *    ~30s (see `POLL_REQUEST_TIMEOUT_MS` above), so raising `timeoutMs` would still be

package/dist/client.js

@@ -625,7 +625,7 @@ export class PipelexApiClient {
      *    other extension route rides the static core (`crate_ops.py` is explicit that
      *    `build/runner` "is the exception — it needs the dry-run sweep"). Giving one
      *    static route an override while its siblings lack one is the inconsistency.
-     * 2. The input is **bounded server-side** — `pipelex-api/api/limits.py` caps a request
+     * 2. The input is **bounded server-side** — the runner's `pipelex_api/limits.py` caps a request
      *    at 16 `.mthds` files of 1 MiB each — and none of these routes runs inference.
      * 3. On the hosted path an override would be **inert**: the gateway caps responses at
      *    ~30s (see `POLL_REQUEST_TIMEOUT_MS` above), so raising `timeoutMs` would still be

package/dist/version.d.ts

@@ -3,4 +3,4 @@
  * `User-Agent` without importing the public barrel. Kept in sync with
  * `package.json` — enforced by `tests/index.test.ts`.
  */
-export declare const SDK_VERSION = "0.28.1";
+export declare const SDK_VERSION = "0.29.1";

package/dist/version.js

@@ -3,5 +3,5 @@
  * `User-Agent` without importing the public barrel. Kept in sync with
  * `package.json` — enforced by `tests/index.test.ts`.
  */
-export const SDK_VERSION = "0.28.1";
+export const SDK_VERSION = "0.29.1";
 //# sourceMappingURL=version.js.map

package/package.json

@@ -1,11 +1,16 @@
 {
   "name": "@pipelex/sdk",
-  "version": "0.28.1",
+  "version": "0.29.1",
   "description": "TypeScript SDK for the Pipelex hosted API — execute methods, manage runs, and call the product surface.",
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "https://github.com/Pipelex/pipelex-sdk-js"
+    "url": "git+https://github.com/Pipelex/pipelex-sdk.git",
+    "directory": "js"
+  },
+  "homepage": "https://github.com/Pipelex/pipelex-sdk/tree/main/js#readme",
+  "bugs": {
+    "url": "https://github.com/Pipelex/pipelex-sdk/issues"
   },
   "type": "module",
   "sideEffects": [