Repository navigation
Release 2.1.0.
Highlights
- npm publication now uses Trusted Publishing (OIDC); the publish workflow requires the
npmenvironment, checks main ancestry, and gates on the MCP surface, release metadata, package contents and runtime audit. Manual dispatch can retry an existing tag. - New registry workflow publishes
server.jsonto the official MCP Registry with GitHub OIDC, a pinnedmcp-publisherand checksum verification. - New
npm run verify:mcpprotocol smoke test andnpm run release:checkmetadata check, both wired into CI on Node 20, 22 and 24. - Runtime
zodupgraded to v4;@types/noderealigned to the Node 20 line; packagerepositorymetadata normalized. - Runtime lockfile refreshed to clear the
body-parserhigh advisory and theqsand@hono/node-servermoderate advisories that kept CI red.
Verification
npm run check (format, lint, types, coverage, build), npm run verify:mcp, npm run release:check, npm audit --omit=dev --audit-level=high and npm pack --dry-run pass. The published package still contains the expected 13 files. Live Chutes integration tests remain opt-in and were not run.
See CHANGELOG.md for details.