Update ToolHive reference docs for v0.21.0#729
Merged
ChrisJBurns merged 1 commit intomainfrom Apr 16, 2026
Merged
Conversation
github-actions
bot
added
the
autogen-docs
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
ChrisJBurns
approved these changes
Apr 16, 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
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.
This PR was auto-generated from ToolHive release v0.21.0. @ChrisJBurns is tagged as the person who cut this release.
What's in this PR
Only machine-generated reference files that are built from the ToolHive source code during the release process:
docs/toolhive/reference/cli/) - help text for everythvcommandstatic/api-specs/toolhive-api.yaml) - OpenAPI/Swagger specdocs/toolhive/reference/crd-spec.md) - Kubernetes CRD referencestatic/api-specs/*.schema.json) - registry validation schemasWhat's NOT in this PR
This PR does not contain guide, tutorial, or conceptual content. Any documentation updates beyond reference files are handled in separate, manually authored PRs.
Review guidance
These files are generated directly from the ToolHive source and are not hand-edited. A quick scan for obvious issues is sufficient - this is intended to be merged shortly after the release is cut so the docs stay in sync.