Skip to content

Update stacklok/toolhive to v0.66.0 - #1344

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

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

Conversation

@renovate

@renovate renovate Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
stacklok/toolhive minor v0.65.0 → v0.66.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.66.0

Compare Source

What's Changed

New Contributors

Full Changelog: stacklok/toolhive@v0.65.0...v0.66.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.66.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.65.0 → v0.66.0
Hand-written changes 0 commit(s)
Reference assets refreshed (separate commit)
Gaps 0
Owner @jhrozek - identified from Release-Triggered-By trailer on the tagged commit
Release contributors 4 review requested (see sidebar) · 1 not requested (no docs impact)
Action required None — approve and merge if the silent-run signal is expected

Who does what

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

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:

Run cost

Session Turns Cost (USD)
Generation 43 $1.3106
Editorial review 14 $0.3358
Total 57 $1.6464
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 16, 2026
@vercel

vercel Bot commented Nov 16, 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 16, 2026 3:56pm UTC

Request Review

@github-actions

Copy link
Copy Markdown
Contributor

Generating docs for toolhive v0.66.0… (run)

@github-actions

Copy link
Copy Markdown
Contributor

Claude generation report

Session status: success · Workflow run

I ran the v0.66.0 release docs workflow unattended. Only one release change needed a page edit; I left the changes uncommitted for the workflow to pick up. Prettier and ESLint are clean and npm run build succeeded.

Doc change

  • I added a "Make the container's root filesystem read-only" section to docs/toolhive/guides-cli/filesystem-access.mdx for the new thv run --read-only-rootfs flag (Add opt-in read-only rootfs for Docker workloads toolhive#7128). It explains:

    • Writable paths: the server can still write to /tmp, /var/tmp and /run, which each get 64 MiB of temporary in-memory space whose files can't be executed. Any volume already mounted at one of those paths is used instead, and the server can also write to its writable volumes and profile write paths.
    • Failures: a server that writes anywhere else fails with a read-only file system error, and the section says how to fix that.
    • Scope: the flag works on Docker and Podman only. The section links to the Kubernetes guide, because the operator already makes the root filesystem read-only there.

    I checked all of this against the PR diff.

Considered and not changed

Artifacts

  • SUMMARY.md lists the edit and each decision above.
  • REVIEWERS.json marks three contributors as needing review, each with a specific thing to check: sathvik8317, tgrunnagle and rdimitrov. It marks jhrozek (the release owner) and tausif-ahmed-guardian as not needing review, with reasons.
  • GAPS.md isn't needed, because nothing depended on context I couldn't get from the source.

The local clone was blocked for both Bash and Read in this session (the Grep tool wasn't available), so I checked behavior against the PR diffs from gh pr diff and the regenerated reference files.

@github-actions

Copy link
Copy Markdown
Contributor

Claude editorial review report

Session status: success · Workflow run

I reviewed the new Make the container's root file system read-only section in docs/toolhive/guides-cli/filesystem-access.mdx and made one small fix. The section is accurate and well placed, and Prettier and ESLint both pass.

Scope: The last commit only changed auto-generated files I'm told not to edit: thv_run.md, the Helm references, and toolhive-api.yaml. So the only page I reviewed is the uncommitted edit to filesystem-access.mdx, which adds the new section.

What I checked:

  • The flag's behavior: The section matches the --read-only-rootfs entry in the thv run reference. That covers Docker and Podman only, a 64 MiB tmpfs for /tmp, /var/tmp, and /run where files can't be executed, a volume taking priority when it targets one of those paths, and writes anywhere else failing.
  • The Kubernetes link: The #mount-a-volume anchor exists in run-mcp-k8s.mdx. That page confirms the operator sets readOnlyRootFilesystem: true by default.
  • Upstream source: I couldn't check the upstream source code because the sandbox blocks reads of the upstream clone. The CLI reference, which is generated from that source, backs up every claim.
  • Writing and structure: The section explains why you'd use the flag, gives a working example with the fetch server, and covers the likely error and how to fix it. It doesn't narrate the release or use dashes, and the page still ends with Next steps, Related information, and Troubleshooting.

What I changed: The page title and body say "file system", but the new section said "filesystem" in three places: the heading, the paragraph after the example, and the Kubernetes note. I changed all three to "file system".

I didn't commit anything; the edit is in the working tree.

@stacklok-octosts
stacklok-octosts Bot marked this pull request as ready for review November 16, 2026 15:53
@github-actions

Copy link
Copy Markdown
Contributor

Done · 57 turns · $1.65 · run · see PR body for details

@aponcedeleonch
aponcedeleonch merged commit bc19189 into main Nov 17, 2026
14 checks passed
@aponcedeleonch
aponcedeleonch deleted the renovate/stacklok-toolhive-0.x branch November 17, 2026 09:29

This branch was successfully deployed

1 active deployment
Preview — dc952d30 Deployed Nov 16, 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