Skip to content

Update stacklok/toolhive to v0.24.1#799

Merged
rdimitrov merged 4 commits intomainfrom
renovate/stacklok-toolhive-0.x
Apr 23, 2026
Merged

Update stacklok/toolhive to v0.24.1#799
rdimitrov merged 4 commits intomainfrom
renovate/stacklok-toolhive-0.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 23, 2026

This PR contains the following updates:

Package Update Change
stacklok/toolhive patch v0.24.0v0.24.1

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 (stacklok/toolhive)

v0.24.1

Compare Source

What's Changed

Full Changelog: stacklok/toolhive@v0.24.0...v0.24.1


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.24.1

At a glance

Upstream stacklok/toolhive v0.24.0v0.24.1
Hand-written changes 2 commit(s)
Reference assets refreshed (separate commit)
Gaps 0
Release contributors 5 auto-assigned · 1 mentioned below
Action required Spot-check skill-authored prose for accuracy

Summary of changes

Summary of changes

  • Added a Capacity limits section to
    docs/toolhive/guides-vmcp/scaling-and-performance.mdx covering the vMCP
    per-pod session cache cap (1,000 concurrent sessions, LRU eviction),
    30-minute inactivity TTL with Redis sliding-window refresh, file-descriptor
    considerations, Redis sizing guidance and default timeouts, and
    stateful-backend data loss on pod restart. Sourced from upstream PR #5025
    and verified against source at the release tag.

No hand edits were needed for the other v0.24.1 changes:

  • The --debug flag fix (#5008), Cedar upstream-claim fix on VirtualMCPServer
    (#5002), and MCPRegistry probe/image bump (#5020) are bug fixes that restore
    or preserve already-documented behavior.
  • The skills content API error classification (#5014) is covered by the
    auto-regenerated OpenAPI spec in static/api-specs/toolhive-api.yaml.

Additional release contributors

Couldn't be auto-assigned as reviewers on this repo, but cc'd below so they see the PR:

@yrobla

Run cost

Session Turns Cost (USD)
Generation 125 $7.2380
Editorial review 47 $3.0158
Total 172 $10.2538
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:

  • docs/toolhive/reference/cli/
  • docs/toolhive/reference/crds/
  • static/api-specs/

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 Apr 23, 2026
@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 23, 2026

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

Project Deployment Actions Updated (UTC)
docs-website Ready Ready Preview, Comment Apr 23, 2026 3:21pm

Request Review

@claude
Copy link
Copy Markdown
Contributor

claude Bot commented Apr 23, 2026

Claude finished @renovate[bot]'s task in 10m 16s —— View job


Upstream release docs for toolhive v0.24.1

All phases complete. Pushed one commit adding hand-written docs for v0.24.1.

  • Phase 1: Release discovery
  • Phase 2: Deep-dive on major changes
  • Phase 3: Docs impact map
  • Phase 4: Hand-written edits
  • Phase 5: Build / lint / verify (Prettier + ESLint clean; Docusaurus build fails in the sandbox on the MCP metadata plugin's external fetch, unrelated to this change)
  • Phase 6: Commit & push (c43a9e4)

What I changed

  • docs/toolhive/guides-vmcp/scaling-and-performance.mdx: added a new ## Capacity limits section covering the per-pod 1,000-session LRU cache, 30-minute inactivity TTL with Redis sliding-window refresh, file-descriptor planning, Redis sizing and default timeouts, and stateful-backend data loss on pod restart. Content sourced from upstream PR #5025 and verified against source at the v0.24.1 tag (pkg/vmcp/server/sessionmanager/factory.go, pkg/vmcp/server/server.go, pkg/transport/session/storage_redis.go, pkg/transport/session/redis_config.go).

What I did not change, and why

PR Reason
#5008 --debug flag in vmcp Bug fix restoring documented behavior; docs never called out that it was broken
#5002 Cedar upstream-claim eval on vMCP Bug fix; existing Cedar claim_* docs already describe the pattern and now simply work on VirtualMCPServer
#5020 MCPRegistry probe port + v1.3.0 image bump Internal chart change; format: appears in docs only in the historical v0.18 migration section
#5014 Skills content API error classification Covered by auto-regenerated static/api-specs/toolhive-api.yaml already in this PR
Internal/infra/release PRs (#5007, #5003, #4998, #5021, #5004, #5024, #5034) No user-facing surface
· Branch

Add a Capacity limits section to the vMCP scaling guide covering the
per-pod 1,000-session LRU cache, 30-minute inactivity TTL with Redis
sliding-window refresh, file-descriptor planning, Redis sizing and
default timeouts, and stateful-backend data loss on pod restart.
Derived from upstream PR stacklok/toolhive#5025 and verified against
source at the v0.24.1 tag.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@claude
Copy link
Copy Markdown
Contributor

claude Bot commented Apr 23, 2026

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


Editorial review of v0.24.1 docs

Applied four editorial fixes to docs/toolhive/guides-vmcp/scaling-and-performance.mdx in commit 57dd409.

File reviewed: docs/toolhive/guides-vmcp/scaling-and-performance.mdx (the only hand-written file in c43a9e4). Auto-generated files (static/api-specs/toolhive-api.yaml, reference/CLI/CRD assets) were excluded per the review scope.

Fixes applied

  • Factual correction: Removed the claim that Redis client timeouts are "tunable through sessionStorage configuration." The SessionStorageConfig CRD struct (cmd/thv-operator/api/v1beta1/mcpserver_types.go L479-L503) only exposes provider, address, db, keyPrefix, and passwordRef. Timeouts are hardcoded Go-side defaults in pkg/transport/session/redis_config.go. Upstream's docs/arch/13-vmcp-scalability.md confirms these are tunable only via RedisConfig.DialTimeout, not the CRD. Replaced the sentence with an accurate note that the defaults are not CRD-exposed.
  • Style: Rewrote two mid-sentence spaced hyphens (Redis sizing, Stateful backend sections) into sentence boundaries, per the CLAUDE.md rule that reserves spaced hyphens for list-style contexts like "Related information" entries.
  • Style: Expanded TTL on first use (### Session time-to-live (TTL)); subsequent references continue to use the acronym.
  • Voice: Flipped "must be reinitialized by the client" to active voice ("the client must reinitialize it").

Not changed, and why

  • Cross-sentence voice and phrasing in the rest of the new section read cleanly and match the file's existing style.
  • Factual claims about the 1,000-session LRU cap, 30-minute inactivity TTL, sliding-window refresh via GETEX, and default 5s/3s/3s timeouts were re-verified against upstream source at v0.24.1 (pkg/vmcp/server/sessionmanager/factory.go:38, pkg/vmcp/server/server.go:74-76, pkg/transport/session/storage_redis.go:49-50,177, pkg/transport/session/redis_config.go:15-19) and upstream's own scalability doc - all accurate, no changes needed.

Prettier formatting could not be run in this environment; all edited lines stay within the 80-character wrap budget, so no rewrap was needed. CI Prettier/ESLint will confirm on push.
· Branch

- Remove inaccurate claim that Redis client timeouts are tunable via
  sessionStorage CRD fields; the CRD does not expose them.
- Rephrase two mid-sentence spaced hyphens per the project style guide.
- Expand TTL acronym on first use.
- Flip one passive-voice sentence to active voice.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 23, 2026

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Copy link
Copy Markdown
Member

@rdimitrov rdimitrov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM from my side

Copy link
Copy Markdown
Contributor

@jhrozek jhrozek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

my part looks good (mechanical changes in swagger)

Copy link
Copy Markdown
Contributor

@samuv samuv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGMT

@rdimitrov
Copy link
Copy Markdown
Member

Merging 🚀

@rdimitrov rdimitrov merged commit 395bfdc into main Apr 23, 2026
6 checks passed
@rdimitrov rdimitrov deleted the renovate/stacklok-toolhive-0.x branch April 23, 2026 22:10
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.

3 participants