From 2935637ed05e7c44c43c56640ca809817ba2e2fc Mon Sep 17 00:00:00 2001 From: Itamar Zand Date: Thu, 30 Jul 2026 17:22:36 +0300 Subject: [PATCH] fix(ci): pack the bindings wrapper with pnpm so workspace ranges resolve MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit npm pack copies package.json verbatim, so the qualified bindings tarball ships "@alienplatform/core": "workspace:^" — a protocol npm rejects at install time. The published bindings 3.2.0 already carries it, and the sdk now depends on the bindings package, so every npm install of the sdk fails with EUNSUPPORTEDPROTOCOL until a corrected version ships. Only pnpm rewrites workspace ranges into the released version while packing; the ai-gateway wrapper below packs this way for the same reason. --- .github/workflows/release.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index b8d56e1d4..55daaa025 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -1150,8 +1150,11 @@ jobs: - name: Inject optionalDependencies into the wrapper run: node packages/bindings/scripts/inject-optional-deps.mjs + # pnpm, not npm: only pnpm rewrites the `workspace:` range on + # `@alienplatform/core` into the released version, and npm rejects a + # published package that still carries the protocol. - name: Pack bindings wrapper - run: npm pack ./packages/bindings --pack-destination "$PWD/qualified/bindings" + run: pnpm --filter @alienplatform/bindings pack --pack-destination "$PWD/qualified/bindings" - name: Upload qualified bindings packages uses: actions/upload-artifact@v6