Drop "Upstream" qualifier from registry schema docs#873
Merged
Conversation
Now that the legacy ToolHive-native registry schema reference has been removed, there is only one registry schema. Rename the page title, navbar entry, and reference index card to "Registry schema" and clean up inline prose accordingly. Kept "Upstream API" as a source type name (federation/aggregation from external registries is a distinct concept). Artifact/file renames are deferred. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
JAORMX
previously approved these changes
May 14, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates ToolHive registry schema documentation labels to remove the now-unhelpful "Upstream" qualifier after the legacy schema reference was removed.
Changes:
- Renames the registry schema page and navigation/card labels.
- Updates inline prose and link text in registry, CLI, and tutorial docs.
- Keeps the underlying schema slug and artifact filenames unchanged.
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
docusaurus.config.ts |
Updates the References navbar label for the registry schema. |
docs/toolhive/tutorials/custom-registry.mdx |
Updates next-step link text for the registry schema reference. |
docs/toolhive/reference/registry-schema-upstream.mdx |
Renames the page title and removes "upstream" from explanatory prose. |
docs/toolhive/reference/index.mdx |
Updates the registry schema reference card label and description. |
docs/toolhive/guides-registry/publish-servers.mdx |
Updates registry schema references throughout publishing guidance. |
docs/toolhive/guides-registry/intro.mdx |
Removes "upstream format" wording from source descriptions where appropriate. |
docs/toolhive/guides-registry/configuration.mdx |
Updates the registry data format link text. |
docs/toolhive/guides-cli/registry.mdx |
Updates custom registry schema references and related prose. |
Address Copilot review feedback on #873 by cleaning up missed schema-qualifier references in the registry quickstart, operator deployment guide, and skills guide. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
JAORMX
previously approved these changes
May 14, 2026
danbarr
reviewed
May 14, 2026
Collaborator
danbarr
left a comment
danbarr
left a comment
There was a problem hiding this comment.
Just one potential addition, but otherwise LGTM!
Co-authored-by: Dan Barr <danbarr@users.noreply.github.com>
danbarr
approved these changes
May 14, 2026
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
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.
Description
With the legacy ToolHive-native registry schema reference removed in #871 (and the redirect restored in #872), there is now only one registry schema in the docs. The "Upstream" qualifier on page/nav titles no longer distinguishes anything and invites the question "upstream of what?"
This PR renames the user-visible labels and cleans up inline prose:
docs/toolhive/reference/registry-schema-upstream.mdx): "Upstream registry JSON schema" -> "Registry JSON schema"docusaurus.config.ts): "Upstream registry schema" -> "Registry schema"docs/toolhive/reference/index.mdx): label and description updatedguides-registry/publish-servers.mdx,guides-registry/configuration.mdx,guides-registry/intro.mdx,guides-cli/registry.mdx, andtutorials/custom-registry.mdxKept intentionally: the "Upstream API" source type name and surrounding federation language in
guides-registry/intro.mdxandguides-registry/configuration.mdx. There, "upstream" means "external MCP Registry API you're syncing from" - a distinct concept that still does work.Deferred (per discussion): artifact/file renames. The file slug
registry-schema-upstream, the JSON schema filenameupstream-registry.schema.json, and the$schemaURLs are referenced bytoolhive-coreand other downstream consumers, so those are a separate coordination.Type of change
Submitter checklist
Content and formatting
Navigation
🤖 Generated with Claude Code