Skip to content

fix: publish the CLI to npm as @harnessprotocol/cli, never @harness-kit/cli - #458

Merged
siracusa5 merged 3 commits into
mainfrom
fix/npm-harness-kit
Nov 11, 2026
Merged

siracusa5 merged 3 commits into
mainfrom
fix/npm-harness-kit

Conversation

@siracusa5

Copy link
Copy Markdown
Collaborator

The @harness-kit npm scope is not ours. @harness-kit/cli and @harness-kit/core belong to an unrelated npm user. The README, the docs, the marketplace install widget and the new Action all pointed people at @harness-kit/cli, which runs that stranger's package.

Changes

  • pnpm run build:cli-npm builds a self-contained harness-kit package. Workspace packages are inlined and third-party dependencies stay external. A packed tarball installs and runs with no workspace present.
  • release.yml publishes it with npm trusted publishing (OIDC, --provenance), with no NPM_TOKEN. It skips a version that already exists, so the first version can be published by hand.
  • The Action runs npx -y harness-kit@0.13.1. The README, the site docs, the install widget and the harness-docs skill all use harness-kit.

Ships as v0.13.1. Before tagging, John publishes 0.13.1 once and links this repo as the trusted publisher on npmjs.com.

Verified: CLI tests (151), core tests (878), website tsc and next build, workflow YAML parses, and the Action script runs against the installed tarball.

🤖 Generated with Claude Code

siracusa5 and others added 2 commits November 8, 2026 18:41
The @harness-kit npm scope belongs to an unrelated user. The README, docs,
marketplace install widget and the Action told people to install or npx
@harness-kit/cli, which runs that stranger's package.

- build a self-contained harness-kit package (workspace packages inlined,
  third-party deps external) with pnpm run build:cli-npm
- release.yml publishes it with npm trusted publishing (OIDC, provenance),
  skipping a version that already exists; no NPM_TOKEN
- the Action runs npx harness-kit@0.13.1; docs and the install widget use
  harness-kit

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
npm refuses harness-kit as too similar to the existing harnesskit package. Publish under the harnessprotocol npm org instead; the commands stay harness-kit and harness. npx needs -p because the bin names differ from the package name. Also restores the space lost in the install widget's run command.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@siracusa5 siracusa5 changed the title fix: publish the CLI to npm as harness-kit, never @harness-kit/cli fix: publish the CLI to npm as @harnessprotocol/cli, never @harness-kit/cli Nov 9, 2026
The @harnessprotocol/cli trusted publisher allows staging only, so the release job runs npm stage publish and a maintainer approves the version on npmjs.com with 2FA. bin paths drop the ./ prefix npm auto-corrects on publish.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@siracusa5
siracusa5 merged commit 4094970 into main Nov 11, 2026
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant