PDPP

publish-mcp-server-package — Tasks

tasks14/18
Created Updated openspec/changes/publish-mcp-server-package/tasks.mdView on GitHub →

1. Manifest and Release-Train Wiring (repo side)

  • 1.1 Remove "private": true from packages/mcp-server/package.json.
  • 1.2 Add publishConfig (access: public, provenance: false, registry: https://registry.npmjs.org/, tag: latest — originally beta, flipped by adopt-single-release-channel) to packages/mcp-server/package.json.
  • 1.3 Strengthen scripts.verify to run tests AND smoke the bin entrypoint (node bin/pdpp-mcp-server.js --help, exit-0 check).
  • 1.4 Add scripts.pack:dry-run to packages/mcp-server/package.json.
  • 1.5 Add pkgRoot: "packages/mcp-server" entry under @semantic-release/npm plugins in .releaserc.yaml.
  • 1.6 Add mcp-server scope entries (feat/fix/perf) to both commit-analyzer and release-notes-generator plugin sections in .releaserc.yaml.

2. README

  • 2.1 Replace the "private workspace package" Publication status paragraph in packages/mcp-server/README.md with the published-package posture paragraph.

3. OpenSpec

  • 3.1 Author openspec/changes/publish-mcp-server-package/proposal.md.
  • 3.2 Author openspec/changes/publish-mcp-server-package/tasks.md.

4. Verification (repo side — run before merge)

  • 4.1 Run pnpm --filter @pdpp/mcp-server run verify — tests pass and --help exits 0.
  • 4.2 Run pnpm --filter @pdpp/mcp-server run pack:dry-run — inspect tarball manifest: only bin/, src/, README.md, and package.json; no test/, node_modules/, or fixture bloat.
  • 4.3 Run node scripts/check-package-release-policy.mjs from repo root — policy check passes for all three publishable packages.
  • 4.4 Run openspec validate publish-mcp-server-package --strict.
  • 4.5 Run openspec validate --all --strict.

5. Owner-Gated Bootstrap (after merge, before the first release cut)

These steps cannot be performed by a repo contributor. They require owner access to the npm organization and the GitHub repository settings.

  • 5.1 [OWNER] On npmjs.com, create the @pdpp/mcp-server package with a placeholder 0.0.0 publish (matching the bootstrap procedure used for @pdpp/cli and @pdpp/local-collector).
  • 5.2 [OWNER] On npmjs.com → @pdpp/mcp-server → Settings → "Publishing access", add the GitHub Actions trusted publisher: vana-com/pdpp repository, semantic-release workflow, release job — matching the existing trusted-publisher entries for @pdpp/cli and @pdpp/local-collector.
  • 5.3 [OWNER] Land a release-worthy Conventional Commit on main (or dispatch the semantic-release workflow) to trigger the release pipeline (single channel; see adopt-single-release-channel).
  • 5.4 [OWNER] Verify npx -y @pdpp/mcp-server@latest --help resolves and exits 0 after the release pipeline completes.