Skip to content

Release MCP 0.10.1 — pin sweep + dogfood autorelease#53

Merged
milstan merged 1 commit into
mainfrom
milstan/post-0.10-cleanup
May 20, 2026
Merged

Release MCP 0.10.1 — pin sweep + dogfood autorelease#53
milstan merged 1 commit into
mainfrom
milstan/post-0.10-cleanup

Conversation

@milstan
Copy link
Copy Markdown
Contributor

@milstan milstan commented May 20, 2026

Summary

Documentation/pin cleanup paired with end-to-end test of the autorelease pipeline now that npm OIDC publishing works.

No functional changes to the published binary. Just bumps every `npx -y @leadbay/mcp@` reference across the repo to `@0.10`, so new installs land on the latest minor:

File Was → Now
`packages/mcp/src/bin.ts` (HELP, install output, claude config, etc.) `@0.3` → `@0.10`
`packages/mcp/README.md` `@0.6` → `@0.10`
`packages/mcp/server.json` (MCP Registry manifest) `@0.9` → `@0.10`
`packages/dxt/manifest.template.json` (.dxt bundle) `@0.9` → `@0.10`
`.claude-plugin/.../plugin.json` `@0.6` → `@0.10`; plugin manifest version → `0.10.1`
Root `README.md` `@0.7` → `@0.10`
Tests asserting the bin.ts pin `@0.3` → `@0.10`

Autorelease validation

Lands as `0.10.1` to exercise the full chain end-to-end:

  1. Merge → `auto-tag.yml` detects `packages/mcp/package.json` change
  2. Pushes `mcp-v0.10.1` tag
  3. Dispatches `release.yml` on the tag
  4. `publish-mcp` (OIDC) → npm
  5. `publish-mcp-registry` (MCP Registry, OIDC) — first time this runs; previous 0.10.0 was dispatched on main and skipped this job
  6. `.dxt` + `.mcpb` uploaded to the GitHub Release

If anything regresses, we'll see it here before the next real feature ship.

Test plan

  • `pnpm -r typecheck` clean
  • `pnpm -F @leadbay/mcp test` — 193 tests pass
  • Merge → confirm `@leadbay/mcp@0.10.1` lands on npm, MCP Registry, and the GitHub Release without intervention
  • Confirm `npm view @leadbay/mcp dist-tags` shows `latest: 0.10.1`

Open follow-up (not in this PR)

  • `@leadbay/leadclaw` still needs a Trusted Publisher binding on npmjs.com (per-package OIDC config). Workflow is already OIDC-ready; only the npm UI config is pending.

🤖 Generated with Claude Code

Doc/pin-only release (no functional changes to the published binary).
Bumps every `npx -y @leadbay/mcp@<old>` reference across the repo to
`@0.10` so new installs land on the latest minor:

- packages/mcp/src/bin.ts (HELP text, install command output, error
  hints, generated claude_desktop_config.json / Claude Code argv,
  doctor instructions) — was @0.3
- packages/mcp/README.md — was @0.6
- packages/mcp/server.json (MCP Registry manifest, version + npx
  identifier) — was @0.9
- packages/dxt/manifest.template.json — was @0.9
- .claude-plugin/.../plugin.json (Claude Code plugin) — was @0.6;
  plugin manifest version bumped to 0.10.1 too
- README.md root — was @0.7

Tests track the bin.ts pin via assertion (install-flags.test.ts,
login-collision.test.ts) — both updated.

Lands as 0.10.1 to dogfood the autorelease chain end-to-end now that
the OIDC plumbing is in place. The auto-tag workflow will push
mcp-v0.10.1 on merge, dispatch release.yml on the tag, and publish
to npm + MCP Registry + the GitHub Release .dxt upload.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@milstan milstan merged commit 0ab7203 into main May 20, 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