Skip to content

Update stacklok/toolhive to v0.57.0 - #1277

Merged
rdimitrov merged 4 commits into
mainfrom
renovate/stacklok-toolhive-0.x
Oct 27, 2026
Merged

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

Conversation

@renovate

@renovate renovate Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
stacklok/toolhive minor v0.56.0 → v0.57.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.57.0

Compare Source

What's Changed

New Contributors

Full Changelog: stacklok/toolhive@v0.56.0...v0.57.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.57.0

At a glance

Upstream stacklok/toolhive v0.56.0 → v0.57.0
Hand-written changes 2 commit(s)
Reference assets unchanged
Gaps 0
Owner @rdimitrov - identified from merged release PR stacklok/toolhive#6947
Release contributors 6 review requested (see sidebar) · 5 not requested (no docs impact)
Action required Spot-check skill-authored prose for accuracy

Who does what

@rdimitrov 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

No docs impact identified

5 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 57 $1.8584
Editorial review 23 $0.5907
Total 80 $2.4491
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>
@renovate renovate Bot added the autogen-docs Pull requests generated by automated release workflows label Oct 27, 2026
@vercel

vercel Bot commented Oct 27, 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 27, 2026 1:20am UTC

Request Review

@github-actions
github-actions Bot marked this pull request as draft October 27, 2026 00:15
@claude

This comment was marked as outdated.

@github-actions

This comment was marked as resolved.

@claude

This comment was marked as outdated.

@github-actions

This comment was marked as resolved.

@claude

claude Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @renovate[bot]'s task in 4m 25s —— View job


Upstream release docs: stacklok/toolhive v0.57.0

  • Phase 1: Discovery
  • Phase 2: Deep dive (verify against source)
  • Phase 3: Audit existing docs
  • Phase 4: Implementation
  • Phase 5: Validation (Prettier, ESLint, and npm run build all pass)
  • Artifacts (REVIEWERS.json, SUMMARY.md)

Changes (commit 9bfc813)

  • Backend-scoped Cedar policies for vMCP (Add backend-scoped vMCP authorization toolhive#6487): added a Backend entity row and a "Backend-scoped tools on a VirtualMCPServer" section to reference/authz-policy-reference.mdx. The section covers resource in Backend::"...", where the backend ID comes from, and what it means for composite tools. Replaced the old warning, which was no longer true, that told readers to match tool-name prefixes. Also added a short example to guides-vmcp/authentication.mdx.
  • dcrConfig.registrationProbe (Add dcrConfig.registrationProbe with an authorization-endpoint strategy toolhive#6834): documented tokenEndpoint (the default), authorizationEndpoint, and none in the re-registration section of guides-k8s/embedded-auth-server-k8s.mdx, and added the field to the DCR table in guides-vmcp/embedded-auth-server-vmcp.mdx.
  • passthroughHeaders: guides-vmcp/configuration.mdx now says headers are read from each request. The page used to say they were captured once per session, which the updated CRD schema shows is no longer true.

Not documented on purpose

Add backend-scoped Cedar policies for vMCP, the DCR
registrationProbe setting, and per-request passthrough
header capture.

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

claude Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

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


Editorial review of v0.57.0 content

  • Identify changed files (5 docs from 9bfc813)
  • Run /docs-review over the changed docs
  • Apply fixes
  • Format and lint (prettier:fix, eslint:fix), commit, push

Summary

The generated content is accurate and well structured. I checked the backend-scoped Cedar content against the upstream docs/authz.md and docs/arch/10-virtual-mcp-architecture.md, and it matches: the Backend parent, no entities_json entry needed, and composite tools having no backend. The registrationProbe table, the passthrough-header capture text, and the new DCR field row read clearly. I found no blocking issues. I pushed four small editorial fixes in 81d5bc8:

docs/toolhive/reference/authz-policy-reference.mdx

  • Changelog framing: "so existing policies are unaffected" became "so policies scoped to the vMCP still match", which describes how it works today instead of framing it as a change.
  • Placeholders: <backend-id> became <backend_id> so it matches the Cedar entity table on the same page.
  • Composite-tools warning: "Express backend restrictions as conditions on permit policies" was vague. It now tells the reader to write the restriction as a condition on their permit policies instead of as a backend-scoped forbid. This is the same guidance as upstream, with no new claims.

docs/toolhive/guides-vmcp/authentication.mdx

  • Placeholder style: <backend-name> became <BACKEND_NAME>, following the style guide's <ALL_CAPS> rule for values the reader supplies.

I didn't touch the auto-generated files (static/api-specs/, reference/helm/, reference/cli/, CRD pages) or the signal files.
• renovate/stacklok-toolhive-0.x

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

@tgrunnagle tgrunnagle left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Ack "skipped consent display_name and refresh-grant hooks" as not needed for public docs.

@rdimitrov
rdimitrov merged commit 43fac08 into main Oct 27, 2026
16 checks passed
@rdimitrov
rdimitrov deleted the renovate/stacklok-toolhive-0.x branch October 27, 2026 14:52

This branch was successfully deployed

1 active deployment
Preview — 81d5bc8b Deployed Oct 27, 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.

6 participants