Repository navigation
Update module github.com/stacklok/toolhive to v0.58.0 - #265
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
Bot
force-pushed
the
renovate/github.com-stacklok-toolhive-0.x
branch
from
October 19, 2026 12:38
635268d to
28d59a5
Compare
renovate
Bot
force-pushed
the
renovate/github.com-stacklok-toolhive-0.x
branch
from
October 20, 2026 17:17
28d59a5 to
5c1adc9
Compare
renovate
Bot
force-pushed
the
renovate/github.com-stacklok-toolhive-0.x
branch
3 times, most recently
from
October 22, 2026 12:05
b7d8f4a to
7a6f20e
Compare
renovate
Bot
force-pushed
the
renovate/github.com-stacklok-toolhive-0.x
branch
from
October 26, 2026 22:09
7a6f20e to
fc3184b
Compare
renovate
Bot
force-pushed
the
renovate/github.com-stacklok-toolhive-0.x
branch
from
October 27, 2026 19:43
fc3184b to
f195f60
Compare
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.52.0→v0.58.0Release Notes
stacklok/toolhive (github.com/stacklok/toolhive)
v0.58.0Compare Source
What's Changed
ca04ba5by @renovate[bot] in #6933Full Changelog: stacklok/toolhive@v0.57.0...v0.58.0
v0.57.0Compare Source
What's Changed
New Contributors
Full Changelog: stacklok/toolhive@v0.56.0...v0.57.0
v0.56.0Compare Source
What's Changed
New Contributors
Full Changelog: stacklok/toolhive@v0.55.2...v0.56.0
v0.55.2Compare Source
Security
Rootless Podman host-access endpoints blocked by the egress proxy (GHSA-2x65-h9w3-h7hc, Medium)
With network isolation on rootless Podman, a workload could reach host services through the Squid or Envoy egress proxy using
host.containers.internalor the address it maps to. ToolHive's protected set only covered Docker's host names and bridge gateways, and Podman's host-access address is not necessarily a bridge gateway.On Podman, ToolHive now reads the DNS sidecar's runtime-generated
/etc/hostsat deployment. It adds every address mapped tohost.containers.internal,host.docker.internal, orgateway.docker.internalto the protected set, alongside all bridge gateways. Both proxies block those names and addresses unless--allow-docker-gatewayis set.What changes for operators
host.containers.internalis missing from the runtime's hosts file (for example withno_hosts = trueincontainers.conf), or if the hosts data cannot be read. This applies even with--allow-docker-gateway.What's Changed
Full Changelog: stacklok/toolhive@v0.55.1...v0.55.2
v0.55.1Compare Source
What's Changed
Full Changelog: stacklok/toolhive@v0.55.0...v0.55.1
v0.55.0Compare Source
What's Changed
f0251ebby @renovate[bot] in #6848Full Changelog: stacklok/toolhive@v0.54.0...v0.55.0
v0.54.0Compare Source
What's Changed
New Contributors
Full Changelog: stacklok/toolhive@v0.53.0...v0.54.0
v0.53.0Compare Source
🚀 Toolhive v0.53.0 is live!
This release adds group-based upstream selection to the vMCP embedded auth server, and stops the operator from acting on
spec.permissionProfileas a security fix. It also makes vMCP keep a backend's valid tools when one of its items can't be decoded, and makes MCPRemoteProxy report config failures correctly.🔄 Deprecations
MCPServer.spec.permissionProfileis deprecated and the Kubernetes operator now ignores it. The field still exists in thev1beta1CRD so existing manifests keep applying, but it never restricted pods in Kubernetes. UsepodTemplateSpecsecurity contexts andNetworkPolicyresources instead. MCPServers that set the field get aPermissionProfileUnsupportedWarning event. No removal version has been announced yet. (security fix, commit d5aa374)🆕 New Features
authserver-config.yaml. It picks which extra upstream providers each user goes through, based on group claims from the first upstream, so users skip OAuth legs for services they have no account on. The feature is opt-in and fails closed when the group claim is missing. CRD support follows in #6740. (#6739)🐛 Bug Fixes
spec.permissionProfileto the runner as a profile name or file path. Before, a crafted value could make the operator read arbitrary local files. Theconfigmapprofile volume is no longer mounted, andthv export --format k8sno longer emits the field. MCPServers that set the field may roll their proxy pods once after upgrading. (d5aa374)Ready=Falsewith a message naming the failing handler and an up-to-dateobservedGeneration. Before, it could showPhase: Failedwhile still reporting a staleReady=True. (#6776)tools/list,resources/list, resource-template and prompt items it cannot decode, and logs a warning naming the backend and the item. Before, one bad item hid all of that backend's capabilities. This applies to the Modern list path only; the Legacy path is tracked in #6814. (#6772)typeis a JSON Schema type array (for example["object","null"]) are now kept, with the schema passed through unchanged, because toolhive-core is bumped to v0.0.52. (#6815)📦 Dependencies
github.com/stacklok/toolhive-coreghcr.io/modelcontextprotocol/inspector(defaultthv inspectorimage)github.com/go-chi/chi/v5github.com/aws/aws-sdk-go-v2github.com/aws/aws-sdk-go-v2/configgithub.com/aws/aws-sdk-go-v2/service/stsgithub.com/pressly/goose/v3github.com/prometheus/commongithub.com/onsi/ginkgo/v2github.com/alicebob/miniredis/v2golang.org/x/cryptogolang.org/x/modgolang.org/x/netgolang.org/x/syncgolang.org/x/sysgolang.org/x/termgolang.org/x/exp/jsonrpc2faecfb2oras.land/oras-go/v2python(e2e test image)create-github-app-token,download-artifact,setup-node,upload-artifact,claude-code-action,codeql-action,goreleaser-action,kind-action)👋 Welcome to our newest contributor: @feiiiiii5 🎉
Full commit log
What's Changed
New Contributors
Full Changelog: stacklok/toolhive@v0.52.0...v0.53.0
🔗 Full changelog: stacklok/toolhive@v0.52.0...v0.53.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.