From 0e2e79ed7ee171324c19908409b1e23385ac7ff9 Mon Sep 17 00:00:00 2001 From: Kevin Hernandez Date: Sat, 13 Jun 2026 16:55:15 +0900 Subject: [PATCH] fix(nix-release): activate pnpm via corepack before CLI deploy The "Package CLI tarball" step invoked raw `pnpm --filter t3 deploy`, but setup-vp embeds pnpm inside Vite+ without exposing a standalone `pnpm` on PATH (and `vp` has no `deploy` command), so the step failed with `pnpm: command not found`. Enable the repo's pinned pnpm via corepack first. Co-Authored-By: Claude Opus 4.8 --- .github/workflows/nix-release.yml | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/.github/workflows/nix-release.yml b/.github/workflows/nix-release.yml index d743b47ab99..f9b2348a9aa 100644 --- a/.github/workflows/nix-release.yml +++ b/.github/workflows/nix-release.yml @@ -51,6 +51,13 @@ jobs: - name: Build CLI run: vp run --filter t3 build + - name: Enable pnpm + # Vite+ embeds pnpm but does not expose a standalone `pnpm` on PATH, + # and `vp` has no `deploy` command. Activate the repo's pinned pnpm + # (the `packageManager` field) via corepack so the deploy step below + # can resolve the production dependency closure. + run: corepack enable + - name: Package CLI tarball run: | mkdir -p release @@ -100,6 +107,13 @@ jobs: - name: Build CLI run: vp run --filter t3 build + - name: Enable pnpm + # Vite+ embeds pnpm but does not expose a standalone `pnpm` on PATH, + # and `vp` has no `deploy` command. Activate the repo's pinned pnpm + # (the `packageManager` field) via corepack so the deploy step below + # can resolve the production dependency closure. + run: corepack enable + - name: Package CLI tarball run: | mkdir -p release