fix: OCI package version in identifier tag (MCP Registry validation)#59
Merged
Conversation
mcp-publisher rejected the package: the MCP Registry requires OCI packages to embed the version as a tag in `identifier` and omit the separate `version` field. - server.json: identifier ghcr.io/aliasunder/vault-mcp → ghcr.io/aliasunder/vault-mcp:0.15.4; removed packages[0].version. - manual_release.yml: the jq bump now sets packages[0].identifier's tag (ghcr.io/aliasunder/vault-mcp:$NEXT) instead of the now-invalid packages[0].version field, keeping the published OCI reference in lockstep with each release. Registry-metadata only — no image rebuild. The :0.15.4 tag already exists on GHCR (deploy.yml pushes the clean-semver tag) and carries the OCI ownership label.
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
2 participants
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
mcp-publisher publishfailed again:The MCP Registry's semantic validation requires OCI packages to put the version in the identifier tag and omit the separate
versionfield (newer than the 2025-12-11 schema we built against).Fix
server.json—packages[0].identifier:ghcr.io/aliasunder/vault-mcp→ghcr.io/aliasunder/vault-mcp:0.15.4; removedpackages[0].version..github/workflows/manual_release.yml— the release jq bump now sets the identifier tag (ghcr.io/aliasunder/vault-mcp:$NEXT) instead of the now-invalidpackages[0].version, so each release keeps the OCI reference in lockstep:Notes
:0.15.4tag already exists on GHCR (deploy.yml pushes the clean-semver tag) and carries theio.modelcontextprotocol.server.nameownership label.version(the server version) is unchanged — only the package version field was disallowed.Validation
jq:packages[0]has noversion; identifier is tagged0.15.5release bump → identifier becomes…:0.15.5, still no package version fieldGenerated by Claude Code