From 507b387d1e134ec86112e5fc1aa74927b640c466 Mon Sep 17 00:00:00 2001 From: Richard Tan Date: Tue, 12 May 2026 02:26:21 +0800 Subject: [PATCH] boxel-cli: publish with pnpm so catalog: deps are resolved MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `npm publish` ships the package.json verbatim, leaving the `catalog:` specifiers in `dependencies` (@aws-crypto/sha256-js, ignore, jsonwebtoken) untouched in the registry tarball. Any consumer install fails: npm: EUNSUPPORTEDPROTOCOL — Unsupported URL Type "catalog:" pnpm: ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER — catalog: only resolves inside the publishing workspace `pnpm publish` rewrites every `catalog:` specifier to its concrete version from pnpm-workspace.yaml's catalog block before uploading, producing a tarball that any installer can consume. This unblocks consumers like boxel-catalog's sync-to-staging GitHub Action (`npm install -g @cardstack/boxel-cli`), which is currently broken on every published version of this package. After merging, cut a new patch release. Existing published versions on npm are not retroactively fixable; consumers will need to pin to the new version (or @latest once it is current). Co-Authored-By: Claude Opus 4.7 (1M context) --- packages/boxel-cli/package.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/boxel-cli/package.json b/packages/boxel-cli/package.json index 62293e78b53..a66e494ff57 100644 --- a/packages/boxel-cli/package.json +++ b/packages/boxel-cli/package.json @@ -74,8 +74,8 @@ "version:patch": "npm version patch", "version:minor": "npm version minor", "version:major": "npm version major", - "publish:npm": "npm publish", - "publish:dry": "npm publish --dry-run" + "publish:npm": "pnpm publish --no-git-checks", + "publish:dry": "pnpm publish --dry-run --no-git-checks" }, "publishConfig": { "access": "public",