From b08c2b2781956af2c2b620a3a4690682608b5b95 Mon Sep 17 00:00:00 2001 From: Richard Tan Date: Tue, 12 May 2026 12:09:37 +0800 Subject: [PATCH] ci(boxel-cli): use pnpm publish in manual release workflow MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The workflow calls `npm publish` directly, bypassing the `publish:npm` script in package.json. As a result the previous fix to that script had no effect — the just-released 0.1.1 tarball still contains raw `catalog:` specifiers in dependencies and is unusable via `npm install`. Switch the workflow's publish step to `pnpm publish` so the catalog protocol is rewritten to concrete versions before the tarball is uploaded. `--no-git-checks` is needed because the workflow has already committed the version bump and tag. The next run will bump to 0.1.2 and publish a clean tarball. Co-Authored-By: Claude Opus 4.7 (1M context) --- .github/workflows/manual-boxel-cli-publish.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/manual-boxel-cli-publish.yml b/.github/workflows/manual-boxel-cli-publish.yml index 20e96be13d2..8a083a447b2 100644 --- a/.github/workflows/manual-boxel-cli-publish.yml +++ b/.github/workflows/manual-boxel-cli-publish.yml @@ -71,9 +71,9 @@ jobs: working-directory: packages/boxel-cli run: | if [ "${{ inputs.environment }}" = "production" ]; then - npm publish --access public --provenance + pnpm publish --access public --provenance --no-git-checks else - npm publish --access public --provenance --tag beta + pnpm publish --access public --provenance --no-git-checks --tag beta fi - name: Create GitHub Release