Skip to content

chore(mcp): 0.2.1 — strip stale pre-release banner#11

Merged
milstan merged 1 commit intomainfrom
milstan/mcp-021
Apr 21, 2026
Merged

chore(mcp): 0.2.1 — strip stale pre-release banner#11
milstan merged 1 commit intomainfrom
milstan/mcp-021

Conversation

@milstan
Copy link
Copy Markdown
Contributor

@milstan milstan commented Apr 21, 2026

0.2.0 shipped with a 'not yet on npm' banner that now renders on https://www.npmjs.com/package/@leadbay/mcp even though the package is live. Removes the banner, the now-obsolete 'install from source' §1.1, and rewrites §7 as a pointer to RELEASE.md. Also the first release carrying signed sigstore provenance (repo is public as of this morning).

…venance release

0.2.0 shipped with a "not yet on npm" banner and an §1.1 "install from
source" fallback section baked into the README. Both were scaffolded for
the bootstrap moment — once 0.2.0 landed on npm they became misleading
(users see the npm page saying "not yet on npm" even though it is).

Changes:
- Remove the pre-release banner at the top of README.md.
- Remove §1.1 "Install from source" — obsolete now that the package is live.
- Rewrite §7 "For maintainers" as a short pointer to RELEASE.md instead of
  duplicating the runbook.
- Drop the LLM-hint line about §1.1 fallback (section no longer exists).

0.2.1 is the first release shipping with signed sigstore provenance
(repo is now public, which unblocks npm's provenance gate).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@milstan milstan merged commit f0f8c7c into main Apr 21, 2026
1 check 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