Skip to content

Update docs for registry server v0.6.3#603

Open
rdimitrov wants to merge 3 commits intomainfrom
registry-updates-via-skill
Open

Update docs for registry server v0.6.3#603
rdimitrov wants to merge 3 commits intomainfrom
registry-updates-via-skill

Conversation

@rdimitrov
Copy link
Member

Description

The following PR content was generated entirely by using the upstream-release-docs skill

  • Update maxMetaSize default from 65536 to 262144 (256 KB) in database and configuration docs
  • Add registry-title annotation to Kubernetes workload discovery docs

Type of change

  • New documentation
  • Documentation update
  • Bug fix (typo, broken link, etc.)
  • Navigation/structure change

Related issues/PRs

Screenshots

Submitter checklist

Content and formatting

  • I have reviewed the content for technical accuracy
  • I have reviewed the content for spelling, grammar, and style

Navigation

  • New pages include a frontmatter section with title and description at a minimum
  • Sidebar navigation (sidebars.ts) updated for added, deleted, reordered, or renamed files
  • Redirects added to vercel.json for moved, renamed, or deleted pages (i.e., if the URL slug changed)

Reviewer checklist

Content

  • I have reviewed the content for technical accuracy
  • I have reviewed the content for spelling, grammar, and style

Copilot AI review requested due to automatic review settings March 10, 2026 14:28
@vercel
Copy link

vercel bot commented Mar 10, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs-website Ready Ready Preview, Comment Mar 10, 2026 4:06pm

Request Review

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates ToolHive Registry Server documentation to reflect registry server v0.6.3 defaults and Kubernetes discovery annotations.

Changes:

  • Update maxMetaSize default from 65536 to 262144 in database and configuration examples/docs.
  • Document the new optional toolhive.stacklok.dev/registry-title annotation for Kubernetes workload discovery, including an updated YAML example.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
docs/toolhive/guides-registry/database.mdx Updates maxMetaSize default in the sample config and the configuration fields table.
docs/toolhive/guides-registry/configuration.mdx Updates maxMetaSize in the main config example and adds the registry-title annotation to the workload discovery section (example + table).

Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.

rdimitrov and others added 2 commits March 10, 2026 18:04
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@danbarr
Copy link
Collaborator

danbarr commented Mar 10, 2026

Good revisions here — this addresses most of the concerns raised in the review of #601.

What's improved:

  • The concept page is much cleaner: the field-dump "Key properties" section is gone, replaced with a clear comparison table and a concrete "When to use skills" section. It reads like a concept page now.
  • The guide is reorganized around tasks ("Discover" / "Publish") rather than endpoint order, and the API reference content has been correctly separated out into a new registry-skills-api.mdx page.
  • The registry overview and configuration pages are updated to mention skills where relevant.

Still missing: the consumer workflow

The primary concern from the previous review is still unresolved. Everything explains how to publish a skill, but there's no explanation of how a skill is actually used once it's in the registry. The packages field points to a git ref or OCI image — but what fetches it? Does the ToolHive CLI have an install command? Does an IDE extension pull from the registry? Is consumption out of scope for this release?

If the tooling for consuming skills isn't ready yet, that's fine — but please say so explicitly. A single sentence would close the gap, something like: "Skill installation via agent clients is planned for a future release; for now, the registry serves as a discovery and distribution layer."

Without that, readers who follow these docs to completion will hit a dead end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants