Visitar URL original
Update stacklok/toolhive-studio to v0.41.0 by renovate[bot] · Pull Request #1331 · stacklok/docs-website · GitHub
Skip to content

Update stacklok/toolhive-studio to v0.41.0 - #1331

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

Update stacklok/toolhive-studio to v0.41.0#1331
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/stacklok-toolhive-studio-0.x

Conversation

@renovate

@renovate renovate Bot commented Nov 13, 2026 •
edited by github-actions Bot
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
stacklok/toolhive-studio minor v0.40.2 → v0.41.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

v0.41.0

Compare Source

What's Changed

Full Changelog: stacklok/toolhive-studio@v0.40.2...v0.41.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.41.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-studio v0.40.2 → v0.41.0
Hand-written changes 0 commit(s)
Reference assets unchanged
Gaps 0
Owner @samuv - identified from release author
Release contributors 1 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

@samuv 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.

Run cost

Session Turns Cost (USD)
Generation 32 $1.0670
Editorial review 14 $0.3876
Total 46 $1.4546
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.

@renovate
Update stacklok/toolhive-studio to v0.41.0
023a6ba 
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 13, 2026
@vercel

vercel Bot commented Nov 13, 2026 •
edited
Loading

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 13, 2026 12:17am UTC

Request Review

@stacklok-octosts
stacklok-octosts Bot marked this pull request as draft November 13, 2026 00:08
@github-actions

github-actions Bot commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

Generating docs for toolhive-studio v0.41.0… (run)

@github-actions

github-actions Bot commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

Claude generation report

Session status: success · Workflow run

I updated the docs for toolhive-studio v0.41.0. The only change readers can see is stacklok/toolhive-studio#2802, so the only page I edited is docs/toolhive/guides-ui/run-mcp-servers.mdx. Prettier and ESLint are clean. I didn't run npm run build and am leaving that to PR CI. I also did a quick self-review instead of the full /docs-review pass, because the change is a single section.

Release triage

What I changed

  • New "Status warnings" section, under "Manage MCP servers": it covers the three labels:

    • Authentication required (unauthenticated)
    • Retrying authentication (auth_retrying)
    • Stopped by policy (policy_stopped)

    It also explains the tooltip that shows the reason when one is available. To recover, you turn the toggle on to restart the server; for a remote server, that runs the sign-in flow again. It links to the authorization method settings in case you need different credentials.

  • Fixed an outdated line: the server card description listed only "Running or Stopped" as statuses. It now says "such as Running or Stopped".

I checked the labels, the warning statuses, the tooltip, and the toggle behavior against the source at v0.41.0. The toggle shows off for any status other than running or starting, and turning it on restarts the server. The local clone wasn't readable, so I fetched the source from the GitHub API at the tag instead.

Handoff files

  • SUMMARY.md is written.
  • REVIEWERS.json is written: samuv is marked docs-facing for commit 3e2edcf, and danbarr is not docs-facing (Context7 config only).
  • No GAPS.md: the PR description covered why the change was made.
  • Neither file shows up in git status, so it looks like git ignores them, as you'd expect for these handoff files.

@github-actions

github-actions Bot commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

Claude editorial review report

Session status: success · Workflow run

I reviewed the only docs change from this release, the new Status warnings section in docs/toolhive/guides-ui/run-mcp-servers.mdx. It needed just one small edit.

The upstream source repo was blocked to me, so I checked the content against the v0.41.0 release notes and upstream PR #2802 ("show auth and policy workload statuses on MCP servers") via gh instead. The section matches the PR:

  • The three labels (Authentication required, Retrying authentication, and Stopped by policy) and what each one means.
  • The warning color in both the card and table views.
  • The tooltip that shows the reason ToolHive reported.
  • The toggle shows as off for these statuses, and turning it on restarts the server. For a remote server, that runs the sign-in flow again.

The writing follows the style guide: no em dashes, no history narration, and second-person voice. The section sits where it belongs, under Manage MCP servers, and the page still ends with its "Next steps" section.

Fix applied: The status bullet in the server card list now links to the new section: "(see Status warnings for authentication and policy statuses)". Without it, a reader only sees Running and Stopped there and has no pointer to the other labels.

npm run prettier:fix and npm run eslint:fix both ran clean. I haven't run the production build, and I haven't committed anything; the change is still uncommitted in the working tree.

@github-actions
github-actions Bot requested a review from samuv November 13, 2026 00:14
@stacklok-octosts
stacklok-octosts Bot marked this pull request as ready for review November 13, 2026 00:14
@github-actions

github-actions Bot commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

Done · 46 turns · $1.45 · run · see PR body for details

This branch was successfully deployed

1 active deployment
Preview — 0046f2e5 Deployed Nov 13, 2026 by vercel[bot]
View deployment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@samuv samuv Awaiting requested review from samuv

At least 1 approving review is required to merge this pull request.

Assignees

@samuv samuv

Labels

autogen-docs Pull requests generated by automated release workflows

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@samuv