Skip to content

Update stacklok/toolhive-studio to v0.35.4#913

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/stacklok-toolhive-studio-0.x
Open

Update stacklok/toolhive-studio to v0.35.4#913
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/stacklok-toolhive-studio-0.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Jun 2, 2026

This PR contains the following updates:

Package Update Change
stacklok/toolhive-studio patch v0.35.3v0.35.4

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

Compare Source

What's Changed

Full Changelog: stacklok/toolhive-studio@v0.35.3...v0.35.4-rc.0

What's Changed

Full Changelog: stacklok/toolhive-studio@v0.35.3...v0.35.4


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

Note

Skill reported no doc-relevant changes for this release.
This PR only bumps the version pin and any pin_files edits.

At a glance

Upstream stacklok/toolhive-studio v0.35.3v0.35.4
Hand-written changes 0 commit(s)
Reference assets unchanged
Gaps 0
Release contributors 2 auto-assigned (see sidebar)
Action required

Run cost

Session Turns Cost (USD)
Generation 18 $0.9941
Editorial review 6 $0.4409
Total 24 $1.4350
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>
@vercel
Copy link
Copy Markdown

vercel Bot commented Jun 2, 2026

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

Project Deployment Actions Updated (UTC)
docs-website Ready Ready Preview, Comment Jun 2, 2026 11:37pm

Request Review

@renovate renovate Bot added the autogen-docs Pull requests generated by automated release workflows label Jun 2, 2026
@github-actions github-actions Bot marked this pull request as draft June 2, 2026 23:50
@claude
Copy link
Copy Markdown
Contributor

claude Bot commented Jun 2, 2026

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


Upstream release docs: toolhive-studio v0.35.4

  • Phase 1: Discover what shipped between v0.35.3 and v0.35.4
  • Phase 2: Deep-dive into the two PRs
  • Phase 3: Build docs impact map (empty - no doc-relevant changes)
  • Phase 4-6: Skipped (no changes required); wrote NO_CHANGES.md

Release analysis

Two PRs shipped in stacklok/toolhive-studio v0.35.4, both internal bug fixes with no impact on documented behavior:

PR Type Why no docs change
stacklok/toolhive-studio#2292 - fix(registry-servers): tag registry installs with registry+server fields Bug fix Internal change to prepareCreateWorkloadData so the workloads API takes the resolveRegistryServer path for registry installs. Fixes an enterprise-only regression where non_registry_servers: false policy gates blocked legitimate registry installs. The function and API tagging are internal implementation details that aren't documented.
stacklok/toolhive-studio#2294 - fix(use-toast-mutation): show error toast when successMsg is null Bug fix Internal React hook (useToastMutation) fix. Error toasts were silently swallowed when callers passed successMsg: null. The hook isn't part of any documented user surface.

Verified by:

  • Reading both PR descriptions and file lists - changes are confined to renderer/src/features/registry-servers/lib/orchestrate-run-registry-server.tsx, renderer/src/common/hooks/use-toast-mutation.ts, and their tests.
  • Searching docs/toolhive/ for references to the affected paths/symbols/concepts - none found except an unrelated mention of the word "toast" in skills-build.mdx (generic UI notification language).

Outcome

Wrote NO_CHANGES.md at repo root signaling no hand-written doc edits are needed for this release. No files were committed (per the skill's contract, the renovate bump is the only change on this branch). Reference assets (CLI help, Swagger, CRD MDX) are unaffected because toolhive-studio doesn't drive those.

@claude
Copy link
Copy Markdown
Contributor

claude Bot commented Jun 2, 2026

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


Editorial review: toolhive-studio v0.35.4

  • Identify files changed by the previous commit
  • Run docs-review pass on those files
  • Apply actionable fixes

Result: nothing to review

The previous Claude session concluded no documentation changes were needed for this release (see prior analysis) and wrote NO_CHANGES.md without committing any docs edits. The only file in HEAD is:

  • .github/upstream-projects.yaml (the renovate version bump from v0.35.3 to v0.35.4)

That's a CI config file, not documentation - no editorial review applies. Per the workflow instructions, NO_CHANGES.md is a signal file for the next pipeline step and isn't mine to edit either.

No commits made on this branch.
| Branch: renovate/stacklok-toolhive-studio-0.x

@github-actions github-actions Bot requested review from peppescg and reyortiz3 June 2, 2026 23:52
@github-actions github-actions Bot marked this pull request as ready for review June 2, 2026 23:52
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.

0 participants