chore: rename CLI package to @leanspec/cli (Part of #254)#311
Merged
Conversation
npm rejected `leanspec` with 403 in workflow run 26144025632:
> Package name too similar to existing package lean-spec
Fall back to the scoped name `@leanspec/cli`, which sits in the same
scope as `@leanspec/mcp`, `@leanspec/http-server`, and the already-
published `@leanspec/cli-{platform}@0.3.0` binary packages. The binary
itself stays named `leanspec` so post-install usage is unchanged
(`leanspec board`, `leanspec init`, etc.).
Update prepare-publish's workspace pkgMap, README quick-start install
command, and the packages/README catalog accordingly.
Part of #254 — unblocks the second publish attempt.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR renames the npm CLI package from the unscoped leanspec to the scoped @leanspec/cli to enable publishing (while keeping the installed binary name leanspec unchanged). It updates publishing preparation logic and user-facing docs so installs and examples reference the new scoped package name.
Changes:
- Rename
packages/clipackage name to@leanspec/cli. - Update
scripts/prepare-publish.tsworkspace package map to resolve@leanspec/cli. - Update root README and
packages/README.mdinstall/usage instructions to use@leanspec/cli.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| scripts/prepare-publish.ts | Updates workspace package name mapping to resolve versions for @leanspec/cli. |
| README.md | Updates Quick Start install/run commands to use @leanspec/cli. |
| packages/README.md | Updates package catalog/usage instructions for the scoped CLI package name. |
| packages/cli/package.json | Renames the published package to @leanspec/cli. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ### Development | ||
|
|
||
| ```bash | ||
| cd rust && cargo build --release |
|
|
||
| # Or try with a tutorial project | ||
| npx leanspec init --example dark-theme | ||
| npx -p @leanspec/cli leanspec init --example dark-theme |
35 tasks
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.
Summary
Recover from the failed second publish attempt (run 26144025632). npm rejected the unscoped
leanspecname with:Use the scoped name
@leanspec/cli, consistent with the existing@leanspec/{mcp,http-server,cli-{platform}}family on npm. The binary stays namedleanspec(Rust[[bin]] name), so user-facing commands (leanspec board,leanspec init, MCP config) are unchanged. Only the install command changes:Updated:
packages/cli/package.jsonnamescripts/prepare-publish.tsworkspacepkgMapREADME.mdQuick Startpackages/README.mdcatalog + per-package section + dev commandNot touching the verification scripts (
scripts/verify-npm-publish.ts,scripts/verify-npm-packages.mjs) — they still reference the unscopedleanspecfor warning checks, but they're non-fatal and pre-date the rename. Follow-up cleanup.State of partial publish:
@leanspec/{cli,mcp,http}-{platform}@0.3.0are on npm.@leanspec/mcp@0.3.0and@leanspec/http-server@0.3.0are on npm.@leanspec/cli@0.3.0needs this PR + a re-trigger ofpublish.yml.@leanspec/ui@0.3.0probably also still pending.Part of #254.
Test plan
npm view @leanspec/cli versionreturns0.3.0npm install -g @leanspec/cli && leanspec --helpworks end-to-end🤖 Generated with Claude Code