Skip to content

Update stacklok/toolhive to v0.59.0 - #1290

Merged
jerm-dro merged 4 commits into
mainfrom
renovate/stacklok-toolhive-0.x
Oct 30, 2026
Merged

jerm-dro merged 4 commits into
mainfrom
renovate/stacklok-toolhive-0.x

Conversation

@renovate

@renovate renovate Bot commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
stacklok/toolhive minor v0.58.0 → v0.59.0

After this PR opens, .github/workflows/upstream-release-docs.yml adds source-verified content edits for the new release. For stacklok/toolhive, the same workflow also syncs reference assets (CLI help, Swagger) and regenerates the CRD MDX pages.


Release Notes

stacklok/toolhive

v0.59.0

Compare Source

What's Changed

Full Changelog: stacklok/toolhive@v0.58.0...v0.59.0


Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.


Docs update for toolhive v0.59.0

At a glance

Upstream stacklok/toolhive v0.58.0 → v0.59.0
Hand-written changes 2 commit(s)
Reference assets refreshed (separate commit)
Gaps 0
Owner @jerm-dro - identified from merged release PR stacklok/toolhive#6977
Release contributors 5 review requested (see sidebar) · 3 not requested (no docs impact)
Action required Spot-check skill-authored prose for accuracy

Who does what

@jerm-dro cut this release and owns this PR: review your own changes, chase the remaining approvals, and merge once they're in. You don't need to wait on a review from anyone listed as having no docs impact below.

Everyone with a review request: the target is a review and approval within 2 business days.

Summary of changes

  • Added TLS configuration for the operator-wide default Redis (operator.defaultRedis.tls) at docs/toolhive/guides-k8s/deploy-operator.mdx, replacing the statement that the default does not support TLS
  • Added a "Re-check the registration while running" section for dcrConfig.registrationProbeInterval at docs/toolhive/guides-k8s/embedded-auth-server-k8s.mdx, and updated the start-only probe wording there
  • Updated the vMCP dcrConfig field table with registrationProbeInterval in docs/toolhive/guides-vmcp/embedded-auth-server-vmcp.mdx
  • Skipped the new delegate_clients[] metadata fields (token_endpoint_auth_method, jwks_file, grant_types, redirect_uris) from Add configured delegate client metadata toolhive#6952: the runner ignores them until the follow-up Wire configured delegate clients into the runner toolhive#6953 ships, and the CRD doesn't expose them
  • Skipped exchange grant storage (Add exchange grant storage with memory backend toolhive#6968): internal storage with no user-facing configuration
  • No prose change for Windows support in thv llm setup --client claude-desktop (Add Windows Claude Desktop credential helper toolhive#6516): no page claimed Windows was unsupported
  • Not swept: Replace removed catalog servers in examples toolhive#6976 says the filesystem server was removed from the registry, but hand-written guides (guides-cli/thvignore.mdx, filesystem-access.mdx, group-management.mdx, guides-mcp/filesystem.mdx) still use thv run filesystem. That removal came from the catalog repo, not this release, so a reviewer should decide on a follow-up

No docs impact identified

3 contributor(s) had no-docs-impact commits in this release. No review was requested, and the workflow did not auto-notify them.

Review routing

GitHub could not request the upstream contributor directly, so review went to the human merger of each relevant upstream PR:

Run cost

Session Turns Cost (USD)
Generation 48 $1.5170
Editorial review 15 $0.4921
Total 63 $2.0091
How this PR was built

Two Claude Opus sessions run per release: a generation pass
(upstream-release-docs skill, 6 phases) followed by a fresh-
context editorial pass (docs-review). Prettier/ESLint
auto-fixes are applied after.

Auto-synced paths — do not hand-edit these in review:

  • static/api-specs/
  • docs/toolhive/reference/cli/ (toolhive only)
  • docs/toolhive/reference/crds/

If a "Gaps needing human context" section is present above,
each entry includes a paste-ready Helper prompt for local
Claude
a reviewer can use to resolve the gap.

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@vercel

vercel Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
docs-website Ready Ready Preview Oct 28, 2026 10:39pm UTC

Request Review

@renovate renovate Bot added the autogen-docs Pull requests generated by automated release workflows label Oct 28, 2026
@github-actions
github-actions Bot marked this pull request as draft October 28, 2026 22:32
@claude

claude Bot commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @renovate[bot]'s task in 3m 1s —— View job


Upstream release docs: stacklok/toolhive v0.59.0

  • Phase 1: Discovery
  • Phase 2: Deep dive (checked against source at v0.59.0) + REVIEWERS.json
  • Phase 3: Audit docs, including a check for existing text this release makes wrong
  • Phase 4: Implement
  • Phase 5: Validate (prettier:fix and eslint:fix pass; I didn't run a site build)
  • Commit and push (46fe06c)

Changes

  • guides-k8s/deploy-operator.mdx: the page said the cluster-wide default Redis doesn't support TLS. That's no longer true, so I replaced it with a section on operator.defaultRedis.tls (Enable TLS for operator-wide Redis defaults toolhive#6838) covering:
    • setting enabled and the optional caCertSecretRef, with key defaulting to ca.crt
    • the chart's checks: TLS needs a Redis address, and a CA Secret needs tls.enabled: true
    • the CA Secret has to exist in each workload's namespace, and a missing Secret shows up as FailedMount
    • a rotated CA in the same Secret only takes effect after the workloads restart
    • a workload with its own spec.sessionStorage ignores the default entirely
  • guides-k8s/embedded-auth-server-k8s.mdx: new "Re-check the registration while running" section for dcrConfig.registrationProbeInterval (Re-check upstream DCR registrations while running toolhive#6948). It covers the 1m minimum, the 5m–15m recommendation, upstream traffic per replica, and the single-use initial access token caveat. I also changed text that said checks happen only at startup.
  • guides-vmcp/embedded-auth-server-vmcp.mdx: added a registrationProbeInterval row to the dcrConfig field table.

Deliberately skipped

Needs a reviewer decision

stacklok/toolhive#6976 says the filesystem server was removed from the registry. Several hand-written guides still use thv run filesystem: thvignore.mdx, filesystem-access.mdx, group-management.mdx, and guides-mcp/filesystem.mdx. The removal happened in the catalog repo, not in this release, and the volume-mount examples have no clear replacement server, so I didn't sweep them. They need a follow-up.

Covers operator.defaultRedis.tls (stacklok/toolhive#6838) and
dcrConfig.registrationProbeInterval (stacklok/toolhive#6948) for v0.59.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@claude

claude Bot commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @renovate[bot]'s task in 1m 19s —— View job


Editorial review of v0.59.0 content edits

  • Find files changed by the previous commit (46fe06c)
  • Run /docs-review on the changed sections
  • Check claims against upstream source
  • Apply fixes, then run prettier:fix and eslint:fix
  • Commit and push

Files reviewed:

  • docs/toolhive/guides-k8s/deploy-operator.mdx: Redis TLS default (operator.defaultRedis.tls)
  • docs/toolhive/guides-k8s/embedded-auth-server-k8s.mdx: new "Re-check the registration while running" section (registrationProbeInterval)
  • docs/toolhive/guides-vmcp/embedded-auth-server-vmcp.mdx: new registrationProbeInterval row in the dcrConfig table

Change made (8dba4a7):

  • embedded-auth-server-k8s.mdx: I rewrote one sentence in the re-check section. It said ToolHive "switches to the result in place," which was vague, and it packed three actions into one sentence. It's now two sentences and says the proxy switches to the new client without restarting.

Checked, no change needed:

  • Upstream admission validation confirms the 1m minimum for registrationProbeInterval (registrationProbeInterval must be at least 1m). That validation also covers VirtualMCPServer, so the vMCP table row is correct.
  • The pages describe current behavior only, with no changelog wording, em dashes, or hedging. The cross-links and anchors line up between the vMCP table and the K8s section.
  • deploy-operator.mdx says the CA Secret belongs in each workload's namespace, "not the operator namespace." I left that negation in because it heads off a likely wrong assumption.

prettier:fix and eslint:fix both ran cleanly. I didn't touch any auto-generated files.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@danbarr danbarr left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Filesystem MCP is being re-added to the catalog (its removal never made it to a shipped catalog+toolhive release); related updates are being handled in #1288

@jerm-dro
jerm-dro merged commit 8325416 into main Oct 30, 2026
13 checks passed
@jerm-dro
jerm-dro deleted the renovate/stacklok-toolhive-0.x branch October 30, 2026 22:33

This branch was successfully deployed

1 active deployment
Preview — 8dba4a7e Deployed Oct 28, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autogen-docs Pull requests generated by automated release workflows

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants