Repository navigation
fix: publish the CLI to npm as @harnessprotocol/cli, never @harness-kit/cli - #458
Merged
Merged
Conversation
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>
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
@harness-kitnpm scope is not ours.@harness-kit/cliand@harness-kit/corebelong 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-npmbuilds a self-containedharness-kitpackage. Workspace packages are inlined and third-party dependencies stay external. A packed tarball installs and runs with no workspace present.release.ymlpublishes it with npm trusted publishing (OIDC,--provenance), with noNPM_TOKEN. It skips a version that already exists, so the first version can be published by hand.npx -y harness-kit@0.13.1. The README, the site docs, the install widget and the harness-docs skill all useharness-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