Skip to content

feat: publish package to npm - #181

Merged
sasan1200 merged 1 commit into
mainfrom
feat/npm-publish
Oct 31, 2026
Merged

sasan1200 merged 1 commit into
mainfrom
feat/npm-publish

Conversation

@sasan1200

Copy link
Copy Markdown
Member

What changed

  • Add publish-npm.yml: on each published GitHub release it checks that the tag matches package.json, skips a version already on npm, runs npm test and npm run verify:package, then runs npm publish --access public --provenance through npm trusted publishing (OIDC, no stored token).
  • README and the installation page install with npm install -g @cavi-ai/ableton-mcp and register the server as ableton-mcp serve; source checkouts remain documented.
  • CHANGELOG entry under Unreleased.

Why

  • @cavi-ai/ableton-mcp is not on the npm registry, so installing requires a source checkout.
  • Publishing requires a trusted publisher on npmjs.com for cavi-ai/ableton-mcp and publish-npm.yml.

Verification

  • npm test (Node 22.13.0 and 24.22.1)
  • npm run verify:package, if packaging, the CLI, or the bridge install changed (Node 22.13.0 and 24.22.1)
  • npm run docs:tools, if a tool contract changed
  • Checked against a running Live, if Live-side behavior changed (Live version: )
  • npm run eval:core (Node 22.13.0 and 24.22.1)
  • npm publish --dry-run --access public: @cavi-ai/ableton-mcp@0.4.0, 347 files, 891.2 kB
  • Release docs build and verify for v0.4.0

Contract impact

  • No tool, resource, or prompt contract change
  • Tool contract changed and reference/tools.md regenerated

@sasan1200
sasan1200 merged commit eab4a9a into main Oct 31, 2026
2 checks passed
@sasan1200
sasan1200 deleted the feat/npm-publish branch October 31, 2026 19:52
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