Repository navigation
Update stacklok/toolhive to v0.61.0 - #1313
Open
renovate[bot] wants to merge 3 commits into
Open
renovate[bot] wants to merge 3 commits into
renovate[bot] wants to merge 3 commits into
Conversation
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
Bot
added
the
autogen-docs
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Generating docs for |
Contributor
|
Done · 40 turns · $1.45 · run · see PR body for details |
jhrozek
approved these changes
Nov 3, 2026
This branch was successfully deployed
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.
This PR contains the following updates:
v0.60.0→v0.61.0After this PR opens,
.github/workflows/upstream-release-docs.ymladds source-verified content edits for the new release. Forstacklok/toolhive, the same workflow also syncs reference assets (CLI help, Swagger) and regenerates the CRD MDX pages.Release Notes
stacklok/toolhive
v0.61.0Compare Source
What's Changed
New Contributors
Full Changelog: stacklok/toolhive@v0.60.0...v0.61.0
Configuration
📅 Schedule: (in timezone America/New_York)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.
Docs update for
toolhivev0.61.0Note
Silent run — skill produced no content commits. The docs are
likely already up-to-date (e.g.
mainahead of pin, or a re-runafter a previous PR for this tag merged). Only the version bump
and refreshed reference assets are included.
At a glance
stacklok/toolhivev0.60.0→v0.61.0Who does what
@ChrisJBurns 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
private_key_jwttoken endpoint section in docs/toolhive/guides-vmcp/delegate-agent-identity.mdx to state that every rejected client assertion (bad signature, unknownkid, wrongaud, reusedjti, expired, futurenbf/iat, or lifetime over the server maximum) returns HTTP 401invalid_client, and that a missingclient_assertionreturns HTTP 400invalid_request(Return invalid_client for failed client assertions toolhive#7036).invalid_clientfromprivate_key_jwtclients in docs/toolhive/guides-vmcp/delegate-agent-identity.mdx.token_exchange.api_audiencereplaced bysubject_token_audiences) and Require offline_access to open an exchange grant toolhive#7038 (offline_access/offlinerequired to open an exchange grant). Both change RunConfig-only delegate client settings: no CRD exposestoken_exchange, no hand-written page documents the exchange-grant flow, and the PR says CRD exposure is still being reworked. The generated API spec (static/api-specs/toolhive-api.yaml) already reflects the new fields. A reviewer should decide whether the RunConfig exchange-grant flow needs a guide once the CRD surface lands.Review routing
GitHub could not request the upstream contributor directly, so review went to the human merger of each relevant upstream PR:
Run cost
How this PR was built
Two Claude Opus sessions run per release: a generation pass
(
upstream-release-docsskill, 6 phases) followed by a fresh-context editorial pass (
docs-review). Prettier/ESLintauto-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.