Skip to content

chore: migrate to mcpb-pack@v3 (drop server.json)#1

Open
mgoldsborough wants to merge 1 commit into
mainfrom
feat/mcpb-pack-v3-migration
Open

chore: migrate to mcpb-pack@v3 (drop server.json)#1
mgoldsborough wants to merge 1 commit into
mainfrom
feat/mcpb-pack-v3-migration

Conversation

@mgoldsborough
Copy link
Copy Markdown

Summary

  • Delete server.json from this bundle. mpak now composes the MCP registry's ServerDetail discovery shape from manifest.json server-side, so the per-bundle file is unused.
  • Drop the workflow step that bumped server.json::version from manifest.json.
  • Bump NimbleBrainInc/mcpb-pack@v2@v3 in the release workflow.

Test plan

  • Cut a release and confirm the build workflow succeeds against mcpb-pack@v3
  • Verify the bundle appears at https://registry.mpak.dev/v1/servers/<name> after announce

mpak now composes the MCP registry's `ServerDetail` discovery shape
from `manifest.json` server-side, so the per-bundle `server.json` file
is no longer used. Drops it, removes the version-bump step that
synced its `version` from `manifest.json`, and bumps the build
workflow to `mcpb-pack@v3`.

Optional follow-up: add a branded reverse-DNS name override in
`manifest.json` under `_meta["dev.mpak/registry"].name` (e.g.
`ai.nimblebrain/<name>` for `@nimblebraininc/*` bundles). Without an
override the registry uses the mechanical default
`dev.mpak.<scope>/<name>`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant