Prepare MCP registry and Glama metadata - #6
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b0dae9fc04
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| assert.equal(serverJson.name, packageJson.mcpName); | ||
| assert.equal(serverJson.packages[0].identifier, packageJson.name); |
There was a problem hiding this comment.
When the next release bumps package.json and the lockfile, every current release check can still pass while both serverJson.version and serverJson.packages[0].version remain at 0.1.3, causing the MCP registry metadata to advertise an obsolete package version. Assert both fields equal packageJson.version so the publish workflow rejects an incomplete version bump.
Useful? React with 👍 / 👎.
1 participant
Summary\n- Add MCP registry server metadata.\n- Add Glama ownership metadata and Docker build support for directory indexing.\n- Add release tests so the metadata stays aligned with package/server identifiers.\n\nValidation\n- npm test\n- npm run check\n- npm run pack:check\n- docker build -t prerenderbuddy-mcp:glama-check .