feat(release): publish @protonspy/csdd-mcp in lockstep with the CLI#5
Merged
Conversation
Build and publish the MCP server alongside the CLI binary as a 7th npm package at the same version, so `make release VERSION=vX.Y.Z` ships everything. - build-packages.mjs stages @protonspy/csdd-mcp from mcp-server/dist: stamps the release version and pins its per-platform optionalDependencies to that exact version (lockstep), dropping scripts/devDependencies from the published manifest (prepublishOnly would otherwise re-run tsc against a src/ we don't ship). - release.yml builds the MCP server before assembling; the existing publish loop (csdd-*) then picks up csdd-mcp with --provenance. - Makefile: add `mcp-dist`; require-version guard on dist/npm-build/release; the manual flow now assembles/publishes 7 packages. - mcp-server/package.json: add repository/homepage/bugs (provenance needs repository). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes the gap from #4: the release pipeline now builds and publishes the MCP server (
@protonspy/csdd-mcp) alongside the CLI binary, as a 7th npm package at the same version — so a singlemake release VERSION=vX.Y.Z(tag → CI) ships everything.Changes
npm/scripts/build-packages.mjs— stages@protonspy/csdd-mcpfrommcp-server/dist: stamps the release version and pins its per-platformoptionalDependenciesto that exact version (lockstep with the binary), and dropsscripts/devDependenciesfrom the published manifest (prepublishOnlywould otherwise re-runtscagainst asrc/that isn't shipped)..github/workflows/release.yml— builds the MCP server (npm ci+tsc) before assembling; the existing publish loop (npm/dist/csdd-*/) then picks upcsdd-mcpwith--provenance.Makefile— addsmcp-dist; therequire-versionguard ondist/npm-build/release(fail fast instead of a cryptictarerror whenVERSIONis left atdev); manual flow now assembles/publishes 7 packages.mcp-server/package.json— addsrepository/homepage/bugs(npm--provenancerequiresrepository).How to cut a release
make release VERSION=v0.2.0 # tag + push → CI builds binaries + publishes all 7 packagesManual fallback:
make dist VERSION=… && make mcp-dist && make npm-build VERSION=… && make npm-publish.Testing
make npm-build VERSION=v0.1.1assembles@protonspy/csdd-mcp@0.1.1with exactoptionalDependenciesand noscripts/devDependencies.npm publish --dry-runon the stagedcsdd-mcp→ OK (10 files, dist + README).npm testgreen (67 tests);make helplists the new targets.Note
@protonspy/csdd-mcpis a new package — theNPM_TOKENautomation token must have rights to create packages in the@protonspyscope (publish uses--access public).🤖 Generated with Claude Code