Skip to content

mdq: publish and run as mdq-cli, fix --help - #259

Merged
DavertMik merged 1 commit into
mainfrom
mdq-cli-name
Sep 29, 2026
Merged

DavertMik merged 1 commit into
mainfrom
mdq-cli-name

Conversation

@DavertMik

Copy link
Copy Markdown
Contributor

The npm package is mdq-cli, but src/utils/mdq/package.json still said mdq. The release workflow would have published under a name the npm trusted publisher doesn't cover, so the publish step would fail.

  • The package name and the installed command are now both mdq-cli (npm i -g mdq-cli, then mdq-cli 'h2' README.md). npx mdq-cli works as before.
  • publish-mdq.yml: the smoke test calls mdq-cli and imports mdq-cli, and the "already published?" check looks up mdq-cli.
  • mdq-cli --help printed only (outputHelp). It now prints the usage and options, with a unit test.
  • README usage lines and CHANGELOG updated.

Verified: bun test tests/unit/mdq/ (222 pass). I also packed dist-mdq, installed the tarball on Node and ran mdq-cli h2 s.md and mdq-cli --help.

After merge, publish a GitHub Release tagged mdq-0.1.2.

🤖 Generated with Claude Code

The npm package is mdq-cli, but the manifest still said mdq, so the
release workflow would publish under a name the trusted publisher does
not cover. The installed command was mdq, which did not match the
package name. Both are now mdq-cli.

--help printed only "(outputHelp)" because the CLI swallows commander
output; it now returns the help text.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@DavertMik
DavertMik merged commit 6c0f416 into main Sep 29, 2026
2 checks passed
@DavertMik
DavertMik deleted the mdq-cli-name branch September 29, 2026 21:58
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