Skip to content

Update stacklok/toolhive to v0.64.0 - #1329

Merged
aponcedeleonch merged 3 commits into
mainfrom
renovate/stacklok-toolhive-0.x
Nov 13, 2026
Merged

aponcedeleonch merged 3 commits into
mainfrom
renovate/stacklok-toolhive-0.x

Conversation

@renovate

@renovate renovate Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
stacklok/toolhive minor v0.61.0 → v0.64.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.64.0

Compare Source

🚀 Toolhive v0.64.0 is live!

This release hardens the embedded authorization server. It closes a client-assertion replay gap, rejects ID-JAGs presented as access tokens, and stops deeply nested JWTs before fosite parses them. The operator now exposes the auth server's TLS listener port.

🆕 New Features

  • When embeddedAuthServer.tlsListener is enabled, MCPServer, MCPRemoteProxy and VirtualMCPServer workloads now get an https-auth container port and a Service port 8443 (appProtocol: https), so the listener can be reached through the Service. Affected workloads roll their pods once on the next reconcile. For a VirtualMCPServer with serviceType: LoadBalancer or NodePort, port 8443 is now reachable from outside the cluster; it serves the same auth server routes already public on the http port. Workloads without the listener don't change (#​7065)

🐛 Bug Fixes

  • private_key_jwt client assertions with exp: 0, an exp that overflows, or presented in the last second before expiry are now refused with HTTP 401 invalid_client. Before, they could be replayed because their jti replay marker had already expired (#​7087)
  • JWTs whose typ marks them as ID-JAGs (oauth-id-jag+jwt) are now rejected wherever an access token is expected, including resource-server bearer auth and token-exchange subject/actor tokens. This prevents token-type confusion when an issuer signs both with the same key (#​7089)
  • Client assertions and OpenID Connect request objects whose payload is not valid JSON, or is nested deeper than 10000 levels, are now refused before fosite parses them. This mitigates the go-jose v3 stack-exhaustion advisory GHSA-vvm8-gf78-28g4 (#​7090)
  • A Redis failure while recording a client assertion's jti now returns the standard OAuth error code server_error instead of error. The HTTP status is still 500 (#​7086)
  • The gjson identity modifiers used by paths like access_token|@upstreamjwt|sub are now registered automatically by authserver.New and upstream.NewOAuth2Provider, so standalone embedders no longer need to register them by hand (#​7063)
  • authserver.New now returns a true nil Server on error instead of a typed-nil pointer. Calling Close more than once no longer repeats cleanup or panics. Storage ownership rules for embedders are now documented (#​7071)
  • Fixed a missing import that kept the auth server storage integration tests from compiling under -tags integration (#​7085)

🧹 Misc

  • CLI help now shows boolean flags as --flag[=true|false] after the spf13/pflag v1.1.0 upgrade. Flag parsing and pass-through of unknown flags are unchanged (#​7083)
  • Added a depguard rule that blocks new non-test imports of go-jose v3 and fosite's token/jwt, so new JWT parsing can't bypass the unsafe-JWS guard (#​7097)
  • The ID-JAG JOSE typ value is now defined once as oauthproto.JWTTypeIDJAG (#​7070)
  • Made the Redis connection-failure tests deterministic by using a client that can never connect, instead of a closed port (#​7080)
  • mockoidc subject assertions in the integration tests now pass with both the old and the new mockoidc versions (#​7078)
  • Raised the golangci-lint CI timeout to 10 minutes (#​7084)
  • Trimmed CODEOWNERS so automatic review requests are opt-in (#​7093)

📦 Dependencies

Module Version
github.com/spf13/pflag v1.1.0
github.com/aws/aws-sdk-go-v2 v1.47.8
github.com/aws/aws-sdk-go-v2/config v1.33.16
github.com/aws/aws-sdk-go-v2/service/sts v1.51.9
github.com/cenkalti/backoff/v7 v7.0.3
github.com/go-jose/go-jose/v4 v4.1.9
github.com/gofrs/flock v0.13.2
github.com/modelcontextprotocol/registry v1.8.8
github.com/onsi/ginkgo/v2 v2.34.0
github.com/stacklok/toolhive-catalog v0.20261103.0
github.com/stacklok/toolhive-core v0.0.59
github.com/stacklok/toolhive-core/redisconn v0.0.59
github.com/testcontainers/testcontainers-go v0.45.0
github.com/tidwall/gjson v1.20.2
modernc.org/sqlite v1.62.0
github.com/oauth2-proxy/mockoidc digest e06ed0b
golang.org/x/exp/jsonrpc2 digest 47ce03d
go.starlark.net digest 4f4267f
alpine 3.24.4
ghcr.io/modelcontextprotocol/inspector 2.14.0
ghcr.io/zizmorcore/zizmor 1.32.0
python, registry, index.docker.io/library/alpine digest updates
node (GitHub Actions) 26
anthropics/claude-code-action v1.0.269
docker/login-action v4.8.0
github/codeql-action v4.39.3
helm/kind-action v1.15.2
sigstore/cosign-installer v4.1.3
Full commit log

What's Changed

Full Changelog: stacklok/toolhive@v0.63.0...v0.64.0

🔗 Full changelog: stacklok/toolhive@v0.63.0...v0.64.0

v0.63.0

Compare Source

What's Changed

Full Changelog: stacklok/toolhive@v0.62.0...v0.63.0

v0.62.0

Compare Source

What's Changed

Full Changelog: stacklok/toolhive@v0.61.0...v0.62.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.64.0

Note

Silent run — skill produced no content commits. The docs are
likely already up-to-date (e.g. main ahead of pin, or a re-run
after a previous PR for this tag merged). Only the version bump
and refreshed reference assets are included.

At a glance

Upstream stacklok/toolhive v0.61.0 → v0.64.0
Hand-written changes 0 commit(s)
Reference assets unchanged
Gaps 0
Owner @aponcedeleonch - identified from Release-Triggered-By trailer on the tagged commit
Release contributors 5 review requested (see sidebar) · 1 not requested (no docs impact) · 1 review routing issue(s)
Action required Yes — manually route 1 unresolved review(s)

Who does what

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

Deferred (judgment calls for the reviewer):

No docs impact identified

1 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:

These reviews require manual routing:

  • Docs-facing commit 9fd68eeb8311 could not be mapped to a merged upstream PR. The release owner must route this review.

Run cost

Session Turns Cost (USD)
Generation 49 $3.0635
Editorial review 22 $0.6041
Total 71 $3.6676
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 Nov 11, 2026
@vercel

vercel Bot commented Nov 11, 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 Nov 12, 2026 3:25pm UTC

Request Review

@stacklok-octosts
stacklok-octosts Bot marked this pull request as draft November 11, 2026 22:04
ChrisJBurns
ChrisJBurns previously approved these changes Nov 11, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Generating docs for toolhive v0.64.0… (run)

@github-actions

Copy link
Copy Markdown
Contributor

Claude generation report

Session status: failure · Workflow run

API Error: 402 request denied by organization policy (budgets-admission): budget exhausted

@github-actions

Copy link
Copy Markdown
Contributor

Failed at generation (failure) · run · see PR body for details

@github-actions

Copy link
Copy Markdown
Contributor

Caution

Docs augmentation failed. Run log.
Retry: gh workflow run upstream-release-docs.yml -f pr_number=1329

@github-actions

Copy link
Copy Markdown
Contributor

Generating docs for toolhive v0.64.0… (run)

@github-actions

Copy link
Copy Markdown
Contributor

Claude generation report

Session status: success · Workflow run

I've updated five doc pages for ToolHive v0.61.0 → v0.64.0, and the production build, Prettier and ESLint all pass. The edits are not committed: git add needed an approval this unattended run can't give, so they're sitting in the working tree for the workflow to commit.

What I changed:

What I left out on purpose (each is listed in SUMMARY.md so a reviewer can overrule it):

Workflow artifacts:

  • SUMMARY.md lists the changes and the items left out.
  • REVIEWERS.json marks 7 of 8 contributors as docs-facing; tgrunnagle is not, because the URL elicitation change has no user-visible trigger.
  • Two of the docs-facing contributors are there only for security fixes I didn't document: reyortiz3 and alex-feel. Their notes ask whether the authorization filter or tool customization docs should mention the new behavior.
  • I didn't write GAPS.md: every feature's purpose could be worked out from the source and PRs.

I didn't run the separate /docs-review skill. I reviewed the diff myself instead.

@github-actions

Copy link
Copy Markdown
Contributor

Claude editorial review report

Session status: success · Workflow run

I reviewed the five guide pages with uncommitted changes from the previous session. Commit f8cc5ad itself only touched auto-generated CLI reference files, so there was nothing in it for me to review. The new content reads well and its claims hold up, so I made two small edits. Prettier and ESLint both ran clean afterwards. I did not commit or push anything.

Fact checks: I couldn't search the local upstream clone because the sandbox blocks that path, so I checked against upstream PRs #7024 and #7065 and the local CRD schema instead. They confirm:

  • The TLS listener uses port 8443, a container port named https-auth, and a Service port with appProtocol: https.
  • Both certificateSecretRef and privateKeySecretRef are required.
  • MCP traffic, health probes, and metrics stay on the HTTP port.
  • An updated certificate is picked up without a pod restart.
  • On a vMCP Service of type LoadBalancer or NodePort, port 8443 is reachable from outside the cluster.
  • The delegateClients[].audiences path in the new troubleshooting row matches the example on the same page.

Two claims I couldn't confirm. Neither contradicts the PRs, so I left them as written:

  • "The listener accepts TLS 1.2 or later" isn't mentioned in either PR or the schema.
  • "The operator marks the workload Failed" when proxyPort is 8443: the PR only says it sets a terminal condition.

Edits:

  • docs/toolhive/guides-k8s/embedded-auth-server-k8s.mdx: the closing VirtualMCPServer paragraph repeated the vMCP guide's note about LoadBalancer and NodePort. It now keeps the spec.authServerConfig.tlsListener path and links to the vMCP guide's new TLS section, so the two pages link to each other.
  • docs/toolhive/guides-vmcp/embedded-auth-server-vmcp.mdx: I moved over the one fact the K8s page dropped: port 8443 serves the same authorization server routes as the HTTP port. This explains the external reachability.

No changes needed: webhooks.mdx, auth-k8s.mdx, and delegate-agent-identity.mdx were clear and in the right place.

@github-actions

Copy link
Copy Markdown
Contributor

Done · 71 turns · $3.67 · run · see PR body for details

@aponcedeleonch
aponcedeleonch merged commit b776a68 into main Nov 13, 2026
14 checks passed
@aponcedeleonch
aponcedeleonch deleted the renovate/stacklok-toolhive-0.x branch November 13, 2026 11:36

This branch was successfully deployed

1 active deployment
Preview — 133a65e0 Deployed Nov 12, 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.

4 participants