Repository navigation
chore: prepare official MCP Registry listing (1.2.11) - #28
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Integrated with original history through #31. Package ownership metadata and server.json are synchronized at 1.2.11, validated against the official Registry schema, and included in the packed artifact. 1.2.11 is now published to npm through the main-branch trusted publishing workflow, with matching commit, tag and fresh installed startup verified. MCP Registry submission remains pending; the metadata is ready, but no Registry listing is claimed. |
Prepare the multi-printer server for listing in the official MCP Registry. Add the matching npm ownership field and registry metadata, including backend configuration and secret credential inputs, in patch release 1.2.11.
Validation: official registry schema validation; npm test (455 passed, 2 optional installed-preset skips); npm run test:package (all three entrypoints, version, and Blender discovery); documentation site build; local standards/spec review. Runtime and printer behavior are unchanged.
Publication must complete through the main-branch trusted-publishing workflow before submitting this version to the registry. The existing workflow currently fails npm authorization; its package publishing settings need verification.