Repository navigation
release: publish as defectdojo-mcp-server - #8
Merged
Merged
Conversation
An unrelated project owns defectdojo-mcp on PyPI, so `uvx defectdojo-mcp` would install it. The distribution becomes defectdojo-mcp-server and keeps the defectdojo-mcp command. The MCP registry name is unchanged. - server.json: PyPI identifier, plus the ghcr image as an OCI package - Dockerfile: io.modelcontextprotocol.server.name label for the registry - release.yml: image tagged with the bare version server.json names, server.json versions checked against the package, registry publish waits for PyPI and the image, mcp-publisher pinned and checksum-verified - README, CONTRIBUTING, CHANGELOG: new install line and publish setup Co-Authored-By: Claude Opus 5.5 <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
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.
Gets the server ready to publish.
An unrelated project already owns
defectdojo-mcpon PyPI, so the README'suvx defectdojo-mcpwould have installed that package, not this server. The distribution is nowdefectdojo-mcp-server. Bothdefectdojo-mcp-serveranddefectdojo-mcpcommands are installed and run the same server. The MCP registry name staysio.github.DefectDojo/defectdojo-mcp.Changes
pyproject.toml: distribution renamed, second console script added.__init__.pyreads its version from the new name.server.json: PyPI identifier updated, and the ghcr image added as an OCI package so Docker users can install from the registry too.Dockerfile:io.modelcontextprotocol.server.namelabel, which the registry checks for OCI packages.release.yml:0.1.0) thatserver.jsonnames;server.json's versions disagree with the package;mcp-publisheris pinned to v1.8.1 and checked against its release checksum instead of downloadinglatest.defectdojo-mcp-server, with a note that thedefectdojo-mcppackage on PyPI is a different project. Docker usesghcr.io/defectdojo/defectdojo-mcp.Testing
ruff,mypy --strictandpytest: 290 passed, 1 skipped.uv build: the wheel isdefectdojo_mcp_server-0.1.0with both entry points.uvx --from <wheel> defectdojo-mcp-server --versionprints 0.1.0.server.jsonvalidates against its schema. The workflow's new version check passes, and fails on a deliberately wrong image tag.docker build: the image has the registry label, and both commands report 0.1.0.To publish (after the repo is public)
defectdojo-mcp-server(ownerDefectDojo, repodefectdojo-mcp, workflowrelease.yml, environmentpypi).pypienvironment in the repo settings.PUBLISH_PYPI,PUBLISH_IMAGEandPUBLISH_MCP_REGISTRYtotrue.v0.1.0. After the image lands, make thedefectdojo-mcpcontainer package public if it isn't already, then re-run the registry job if it failed on visibility.🤖 Generated with Claude Code