Repository navigation
Release hygiene: CLI version string, linked-version docs, npm discoverability #169
Description
Release hygiene:
- CLI
--versionprints 0.1.0 (hard-coded.version("0.1.0"),packages/cli/src/cli.ts:30) while the package is 0.3.3. Read it from package.json. - RELEASING.md "linked set" claim is wrong in practice. It says the linked packages always share a version; npm now has merchant 0.10.2, mcp 0.10.1, core/agent 0.10.0. Changesets
linkedonly equalizes packages bumped in the same release. Either document that accurately or switch tofixed. - npm discoverability:
scope:pincerpaysearch returns nothing, andmaintainer:pincerpaydlists 7 packages but omits@pincerpay/solana. Check package metadata/maintainers for@pincerpay/solana.
Source: Grok read-only repo audit, _planning/research/PINCERPAY_REFERENCE.md §17 (2026-10-29); verified against master cb86833.
Activity
ds1 commentedon Oct 30, 2026
Item 3 (npm search):
@pincerpay/solanahas the same maintainer (pincerpayd), repository andpublishConfigas its siblings, so the gap is npm-side search indexing, not package metadata. No code change. Items 1 (CLI version) are in #173-pending PR; item 2 (linked vs fixed) is in the docs/versioning PR.ds1 commentedon Oct 30, 2026
Resolved: (1) CLI
--versionand MCP server version read package.json, shipped in #173 (cli 0.3.4, mcp 0.10.3). (2) Changesets moved fromlinkedtofixedwith RELEASING.md updated in #175; release 0.10.3 aligned core/agent/merchant/mcp. (3) npm search gap is npm-side indexing, not package metadata (see earlier comment). Follow-ups: #174.