chore(registry): bump server.json to the 2025-12-11 schema#54
Merged
Conversation
The pinned 2025-07-09 schema is two releases stale and the current registry rejects the old field names — validated locally with ajv against the live 2025-12-11 schema: the old file FAILS (packages[0] must have required property 'registryType'), the new one passes. Changes: registry_type→registryType, website_url→websiteUrl, drop the removed 'status' field. Publishing is unblocked now that @starter-series/create@0.4.0 is live on npm (the registry cross-checks package.json#mcpName, already set).
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
1 participant
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.
The
server.json$schema pinned 2025-07-09 — two releases stale. Validated with ajv against the live 2025-12-11 schema (fetched today):packages[0] must have required property 'registryType'(snake_case fields were renamed)Changes:
registry_type→registryType,website_url→websiteUrl, drop the removedstatusfield. With@starter-series/create@0.4.0now live on npm (andpackage.json#mcpNamematching), the registry's ownership cross-check is satisfied — after merge, dispatching Publish to MCP Registry (GitHub OIDC, zero secrets) completes the listing.