Update stacklok/toolhive-studio to v0.38.0 by renovate[bot] · Pull Request #1037 · stacklok/docs-website

renovate · 2026-07-16T18:08:26Z

This PR contains the following updates:

Package	Update	Change
stacklok/toolhive-studio	minor	`v0.37.0` → `v0.38.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-studio (stacklok/toolhive-studio)

`v0.38.0`

Compare Source

What's Changed

fix(deps): update dependency react-hook-form to v7.81.0 by @renovate[bot] in #2445
chore(deps): update pnpm to v11.10.0 - autoclosed by @renovate[bot] in #2444
chore(deps): update aws-actions/configure-aws-credentials digest to 517a711 by @renovate[bot] in #2443
chore(deps): update anthropics/claude-code-action digest to 37b464c by @renovate[bot] in #2432
chore(deps): update dependency fast-xml-builder to >=1.2.1 by @renovate[bot] in #2446
fix(deps): update dependency @ai-sdk/openai to ^4.0.8 by @renovate[bot] in #2447
feat(ci): add DigiCert signing flag to PR build-test by @samuv in #2451
chore(deps): update vitest monorepo to ^4.1.10 by @renovate[bot] in #2448
chore(deps): update dependency typescript-eslint to ^8.63.0 by @renovate[bot] in #2449
chore(deps): update dependency @types/node to ^24.13.3 by @renovate[bot] in #2453
chore(deps): update dependency prettier to v3.9.5 by @renovate[bot] in #2454
fix(deps): update ai stack by @renovate[bot] in #2457
chore(deps): update dependency vite to ^8.1.4 by @renovate[bot] in #2456
chore(deps): update dependency msw to ^2.15.0 by @renovate[bot] in #2463
chore(deps): update dependency prettier-plugin-classnames to ^0.10.4 by @renovate[bot] in #2455
fix(deps): update radix-ui-primitives monorepo by @renovate[bot] in #2458
chore(deps): update dependency electron to v43.1.0 by @renovate[bot] in #2460
chore(deps): update dependency knip to ^6.26.0 by @renovate[bot] in #2461
chore(deps): update dependency @electron/rebuild to ^4.2.0 by @renovate[bot] in #2459
chore(deps): update dependency memfs to ^4.64.0 by @renovate[bot] in #2462
fix(ci): don't fail unit tests job on Coveralls upload errors by @samuv in #2464
fix(deps): update dependency @sentry/vite-plugin to ^5.4.0 by @renovate[bot] in #2468
chore(deps): update dependency stacklok/toolhive to v0.36.0 by @renovate[bot] in #2465
chore(deps): update anthropics/claude-code-action digest to 1253134 by @renovate[bot] in #2452
chore(deps): update actions/setup-node digest to 2499707 by @renovate[bot] in #2466
fix: make network isolation mode explicit instead of inferred by @kantord in #2469

Full Changelog: stacklok/toolhive-studio@v0.37.0...v0.38.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-studio` v0.38.0

At a glance


Upstream	`stacklok/toolhive-studio` `v0.37.0` → `v0.38.0`
Hand-written changes	2 commit(s)
Reference assets	unchanged
Gaps	1
Release contributors	2 auto-assigned (see sidebar)
Action required	Yes — resolve 1 gap(s), then spot-check prose

Summary of changes

Updated the Studio network isolation guide in
docs/toolhive/guides-ui/network-isolation.mdx to reflect the new
Network access tab: 3-way mode radio (No isolation / Host networking
(Advanced) / Isolate behind an HTTP proxy), nested "Allowed destinations"
radio (Anywhere / Selected destinations), and the corresponding default
behavior for registry vs custom servers.
Reworked the "info: Important" empty-allow-list admonition,
troubleshooting steps, and cross-network example on the same page to
describe the new proxy-mode-only scoping instead of the boolean toggle.
Renamed the ### Network isolation section in
docs/toolhive/guides-ui/configure-mcp-servers.mdx to ### Network access
and rewrote its blurb to match the new tab label and mode semantics.

Gaps needing human context

Network access screenshot refresh (PR stacklok/toolhive-studio#2469 by @kantord)

The Studio "Network access" tab UI was rewritten in v0.38.0: the boolean
network isolation toggle became a 3-way radio (No isolation / Host networking
(Advanced) / Isolate behind an HTTP proxy) with a nested "Allowed destinations"
radio. The existing static/img/toolhive/network-isolation-{light,dark}.webp
screenshots on docs/toolhive/guides-ui/network-isolation.mdx show the old
toggle-and-list UI and no longer match what the reader sees. Refresh both
themes with a screenshot of the new UI in "Isolate behind an HTTP proxy" +
"Selected destinations" mode, showing populated Allowed hosts and Allowed
ports (the same example the prose describes: api.github.com,
.githubusercontent.com, port 443).

File(s): static/img/toolhive/network-isolation-light.webp,
static/img/toolhive/network-isolation-dark.webp,
docs/toolhive/guides-ui/network-isolation.mdx

Helper prompt for local Claude:

Refresh the Network access screenshots referenced from
docs/toolhive/guides-ui/network-isolation.mdx (both light and dark themes
at static/img/toolhive/network-isolation-light.webp and
network-isolation-dark.webp). Context: stacklok/toolhive-studio#2469
replaced the boolean toggle with a 3-way "Network access" radio + nested
"Allowed destinations" radio in v0.38.0, so the existing screenshots are
stale. Capture the new UI in "Isolate behind an HTTP proxy" +
"Selected destinations" mode with the example values already documented on
the page (api.github.com, .githubusercontent.com, port 443). Replace
both .webp files in place - the page's <ThemedImage> block already
references the correct paths and needs no MDX changes.

Run cost

Session	Turns	Cost (USD)
Generation	61	$4.4936
Editorial review	31	$2.3292
Total	92	$6.8228

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)

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 · 2026-07-16T18:08:32Z

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

Project	Deployment	Actions	Updated (UTC)
docs-website	Ready	Preview, Comment	Jul 16, 2026 6:48pm

claude · 2026-07-16T18:23:32Z

Claude finished @renovate[bot]'s task in 7m 35s —— View job

Upstream release docs: stacklok/toolhive-studio v0.38.0

Ran /upstream-release-docs in unattended mode.

Phase 1: Discovery — categorize release changes
Phase 2: Deep dive on PRs (source-verified)
Phase 3: Audit existing docs, build impact map
Phase 4: Implement doc changes
Phase 5: Validate (prettier + eslint clean; npm run build fails on an unrelated mcp-metadata-plugin network fetch in this sandbox — real CI has the required network access)
Phase 6: Push commit / write artifacts

Summary

v0.38.0's only doc-relevant change is stacklok/toolhive-studio#2469 by @kantord: the Studio's boolean network isolation toggle became a 3-way Network access radio (No isolation / Host networking (Advanced) / Isolate behind an HTTP proxy) with a nested Allowed destinations radio (Anywhere / Selected destinations). Verified against renderer/src/features/network-isolation/components/network-access-tab-content.tsx and the tab triggers in dialog-form-local-mcp.tsx and form-run-from-registry/index.tsx at v0.38.0. Registry-server default is proxy; custom local server default is none.

The "Allow host machine access" checkbox is UI-only in this release (per PR author) — the backend has no REST-reachable allow_docker_gateway field on create/update yet — so it's intentionally omitted from the docs and the existing host.docker.internal guidance is preserved.

Everything else in the release is dependency updates and CI infra with no user-facing surface.

Changes

Commit cbbdef3:

Updated docs/toolhive/guides-ui/network-isolation.mdx — rewrote the "Enabling network isolation" section as "Configuring network access", describing the 3-way mode radio and per-mode defaults (registry vs custom). Added a "Restricting proxied traffic" subsection covering the Allowed destinations radio. Adjusted the empty-allow-list admonition, cross-network example, and troubleshooting step to scope to proxy mode.
Updated docs/toolhive/guides-ui/configure-mcp-servers.mdx — renamed the ### Network isolation heading to ### Network access with an updated blurb, and refreshed the frontmatter description.

Deferred (`GAPS.md`)

The existing themed screenshots at static/img/toolhive/network-isolation-{light,dark}.webp show the old toggle UI and need regenerating from the new radio-based UI. Cannot be produced by this bot; entry recorded in GAPS.md with a paste-ready helper prompt for a human reviewer.
· Branch

toolhive-studio v0.38.0 replaces the boolean network isolation toggle with a 3-way network access radio (none / host / proxy) and a nested allowed destinations radio (anywhere / selected). Rewrite the Studio network isolation guide and the configure-mcp-servers section to match the new UI and defaults.

claude · 2026-07-16T18:31:24Z

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

Editorial review of upstream release docs

Applied /docs-review polish over commit cbbdef3 and pushed f58f03d.

Fixes applied

docs/toolhive/guides-ui/network-isolation.mdx

Line 63 - "an Allowed destinations radio appears" → "the Allowed destinations options appear". Bare "radio" is UI/dev shorthand for "radio button group"; end-user docs should name the UI element the way a reader would perceive it.
Line 66 - "If Selected destinations is chosen" → "When you choose Selected destinations". Style guide requires active voice / second person.
Line 99 - "the form displays a warning when this configuration is detected" → "the form displays a warning in this case". Trimmed a filler passive clause.

docs/toolhive/guides-ui/configure-mcp-servers.mdx

Line 131-133 - Rebalanced the three-item list under ### Network access. The third item ("routing outbound HTTP and HTTPS traffic through ToolHive's egress proxy so it can only reach the destinations you allow") swelled a two-word / two-word / 19-word list. Compressed to "an HTTP proxy that restricts outbound traffic to destinations you allow", deferring detail to the linked guide.

Skipped intentionally

Frontmatter description: "How to configure network isolation..." on network-isolation.mdx - unchanged by this PR, out of scope for the release-driven review.
The :::info[Proxy compatibility] block positioned above the mode-selection section - post-PR its subject (HTTP_PROXY env vars) applies only to the proxy mode, but the guide's overall topic is still proxy-based isolation and the block reads correctly in context. Reworking placement would be a separate cleanup.
Screenshot at static/img/toolhive/network-isolation-{light,dark}.webp - still shows the pre-v0.38.0 toggle UI. Already recorded in GAPS.md by the prior session for human follow-up.
**Host networking (Advanced)** full label vs. the shorter **Host networking** used in the intro :::note - the note is conversational and readers will still recognize the button; not worth the churn.
· Branch

danbarr · 2026-07-16T18:39:56Z

@claude I'm pretty sure this statement is not true and that note on the PR was just outdated; the version of the API included with this UI release does indeed have the docker gateway field wired up and it should be wired through...verify and fix the docs if so.

The "Allow host machine access" checkbox is UI-only in this release (per PR author) — the backend has no REST-reachable allow_docker_gateway field on create/update yet — so it's intentionally omitted from the docs and the existing host.docker.internal guidance is preserved.

The generation agent also missed the crux of the change here; network isolation (which is still the name of the feature, for consistency with the CLI) is now enabled by default. This matches the same default-enabled state that CLI v0.30.1 brought.

claude · 2026-07-16T18:40:42Z

Claude finished @danbarr's task in 6m 45s —— View job

Fixed: network access docs for toolhive-studio v0.38.0

Both of your points check out against the source I could reach. Pushed 6cd0e39.

Claim 2 — isolation enabled by default: CONFIRMED and fixed. The vendored API spec (static/api-specs/toolhive-api.yaml) states on both createRequest and updateRequest: "omitting the field defaults to network isolation ENABLED (matching the thv run CLI default)." The CLI guide agrees ("From v0.30.1 onward, isolation is the default... and for workloads created through the REST API"). The generation agent's "custom servers default to No isolation" was wrong.
Claim 1 — "Allow host machine access" is real and wired: CONFIRMED and documented. allow_docker_gateway exists in the API and the CLI already documents --allow-docker-gateway. The key detail: Docker gateway addresses (host.docker.internal, etc.) are blocked by an explicit deny even when all destinations are allowed - so the prior UI guidance ("add host.docker.internal to Allowed hosts") was actually incorrect. That guidance is now replaced with the checkbox.
Fixed docs/toolhive/guides-ui/network-isolation.mdx
Fixed docs/toolhive/guides-ui/configure-mcp-servers.mdx
Prettier + ESLint clean; committed and pushed

Changes made

network-isolation.mdx

Intro now states ToolHive enables network isolation by default for local servers, matching the CLI; new servers start behind the HTTP proxy.
Per-mode defaults corrected: both registry and custom servers default to Isolate behind an HTTP proxy (was "custom servers default to No isolation").
New Allowing host machine access subsection documenting the checkbox: gateway addresses are blocked by default even when all destinations are allowed, the option is port-independent, and you don't add the gateway hostname to allowed hosts.
Rewrote Accessing other workloads on the same container network to point at the checkbox instead of the (incorrect) "add host.docker.internal to Allowed hosts" instruction.
Added a host-machine-access check to the troubleshooting step.

configure-mcp-servers.mdx

### Network access blurb now leads with network isolation being on by default and routing through the HTTP proxy.

Notes / caveats

The sandbox blocks network access, so I could not fetch the toolhive v0.36.0 source bundled in studio v0.38.0 directly. I verified against the vendored v0.35.0 API spec + the CLI guide (both already reflect default-on isolation and the allow_docker_gateway semantics) and relied on your maintainer confirmation that the field is REST-reachable on create/update in v0.36.0. The doc prose describes the UI checkbox behavior, so it holds regardless of the exact API plumbing.
I kept the Network access tab/heading name (it matches the literal UI tab label) while making sure the prose preserves the "network isolation" concept and its default-on posture, per your consistency note.
The stale screenshots at static/img/toolhive/network-isolation-{light,dark}.webp still show the old toggle UI - unchanged here, still tracked as the outstanding gap for a human to regenerate.
· Branch

Network isolation is enabled by default (matching the CLI since v0.30.1 and the REST API default), so both registry and custom servers start behind the HTTP proxy. Document the Allow host machine access option, which maps to allow_docker_gateway: Docker gateway addresses are blocked by an explicit deny even when all destinations are allowed, so the prior guidance to add host.docker.internal to the allowed hosts list was incorrect. Co-authored-by: Dan Barr <danbarr@users.noreply.github.com> Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

samuv · 2026-07-17T14:48:48Z

@kantord does the generated doc look good?

Update stacklok/toolhive-studio to v0.38.0

8621c7f

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

renovate Bot added the autogen-docs Pull requests generated by automated release workflows label Jul 16, 2026

github-actions Bot marked this pull request as draft July 16, 2026 18:08

This comment was marked as outdated.

Sign in to view

vercel Bot deployed to Preview July 16, 2026 18:09 View deployment

This comment was marked as outdated.

Sign in to view

github-actions Bot requested review from kantord and samuv July 16, 2026 18:14

github-actions Bot marked this pull request as ready for review July 16, 2026 18:14

github-actions Bot marked this pull request as draft July 16, 2026 18:23

vercel Bot deployed to Preview July 16, 2026 18:32 View deployment

Editorial polish for network access docs

f58f03d

github-actions Bot marked this pull request as ready for review July 16, 2026 18:36

vercel Bot deployed to Preview July 16, 2026 18:36 View deployment

vercel Bot deployed to Preview July 16, 2026 18:48 View deployment

samuv approved these changes Jul 17, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Update stacklok/toolhive-studio to v0.38.0#1037

Update stacklok/toolhive-studio to v0.38.0#1037
renovate[bot] wants to merge 4 commits into
mainfrom
renovate/stacklok-toolhive-studio-0.x

renovate Bot commented Jul 16, 2026 •

edited by github-actions Bot

Loading

Uh oh!

vercel Bot commented Jul 16, 2026 •

edited

Loading

Uh oh!

This comment was marked as outdated.

This comment was marked as outdated.

claude Bot commented Jul 16, 2026 •

edited

Loading

Uh oh!

claude Bot commented Jul 16, 2026 •

edited

Loading

Uh oh!

danbarr commented Jul 16, 2026

Uh oh!

claude Bot commented Jul 16, 2026 •

edited

Loading

Uh oh!

samuv commented Jul 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

renovate Bot commented Jul 16, 2026 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v0.38.0

What's Changed

Configuration

Docs update for toolhive-studio v0.38.0

At a glance

Summary of changes

Gaps needing human context

Network access screenshot refresh (PR stacklok/toolhive-studio#2469 by @kantord)

Run cost

Uh oh!

vercel Bot commented Jul 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

This comment was marked as outdated.

This comment was marked as outdated.

claude Bot commented Jul 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Upstream release docs: stacklok/toolhive-studio v0.38.0

Summary

Changes

Deferred (GAPS.md)

Uh oh!

claude Bot commented Jul 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Editorial review of upstream release docs

Fixes applied

Skipped intentionally

Uh oh!

danbarr commented Jul 16, 2026

Uh oh!

claude Bot commented Jul 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Fixed: network access docs for toolhive-studio v0.38.0

Changes made

Notes / caveats

Uh oh!

samuv commented Jul 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

renovate Bot commented Jul 16, 2026 •

edited by github-actions Bot

Loading

`v0.38.0`

Docs update for `toolhive-studio` v0.38.0

vercel Bot commented Jul 16, 2026 •

edited

Loading

claude Bot commented Jul 16, 2026 •

edited

Loading

Deferred (`GAPS.md`)

claude Bot commented Jul 16, 2026 •

edited

Loading

claude Bot commented Jul 16, 2026 •

edited

Loading