Skip to content

fix: rename acture-mcp → acture-mcp-server (npm name collision) - #11

Merged
thorwhalen merged 1 commit into
mainfrom
fix/acture-mcp-server-rename
May 14, 2026
Merged

thorwhalen merged 1 commit into
mainfrom
fix/acture-mcp-server-rename

Conversation

@thorwhalen

Copy link
Copy Markdown
Member

Summary

The unscoped name acture-mcp is already taken on npm by an unrelated project (vkhafizov, "MCP server … narrative reports", 1.0.5), so changeset publish skipped our package. Renamed the MCP adapter to acture-mcp-server across package.json, imports, workspace deps, changeset config, examples, docs, and skills.

All 15 packages are now live on npm:

  • acture@1.1.0, eslint-plugin-acture-migration@1.0.0 (published earlier)
  • 12 acture-* packages published in v1.5
  • acture-mcp-server@1.0.0 published after this rename

docs/roadmap.md and docs/next_session.md updated to reflect the rename and that publishing is complete.

Test plan

  • pnpm build — all 15 packages build
  • pnpm test — 396 package tests green
  • example tests — 41 green
  • pnpm typecheck — clean across all 15 packages
  • acture-mcp-server@1.0.0 published successfully to npm

The unscoped name `acture-mcp` is already taken on npm by an unrelated
project (vkhafizov, "MCP server … narrative reports", 1.0.5), so
`changeset publish` skipped it. Renamed the MCP adapter package to
`acture-mcp-server` across package.json, imports, workspace deps,
changeset config, examples, docs, and skills. All 15 packages now
publish cleanly and are live on npm.

396 package tests + 41 example tests green; all packages build + typecheck.
@thorwhalen
thorwhalen merged commit 235b796 into main May 14, 2026
1 check passed
@thorwhalen
thorwhalen deleted the fix/acture-mcp-server-rename branch May 14, 2026 11:29
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