v0.38.0

@pipelex/sdk on npm

Fixed

• js/'s lockfile installs under npm 10: package-lock.json is a valid install tree again, so npm ci in js/ installs it under the npm that Node 22 bundles, where it stopped with EUSAGE because vite 8's optional esbuild peer could not share the esbuild 0.25 the package pinned; esbuild moves to 0.28, which the hook bundle built by npm run build:hook is now built with. make install installs from the lockfile with npm ci and no longer rewrites it, make use-local no longer rewrites the mthds-js checkout's lockfile either, and make check runs a new make check-lock, which refuses a lockfile whose tree npm ls calls invalid and names the dependency at fault.

pipelex-sdk on PyPI

Changed

• Requires mthds 0.21.0, the release that reports MTHDS standard 5.0.0 (Breaking): the exact pin moves from mthds==0.20.0 to mthds==0.21.0, so every environment holding this pipelex-sdk installs exactly that mthds, and a project that also pins mthds itself has to move with it. The release's one behavioural change is MTHDS_STANDARD_VERSION going from 4.0.0 to 5.0.0, which this client never reads, so nothing in pipelex-sdk's own surface changes and PROTOCOL_VERSION stays where it was. Code of your own that checks a manifest's mthds_version with mthds now evaluates it against 5.0.0, where a constraint of ^4.0.0, ~4.0.0, 4.* or exactly 4.0.0 no longer passes.