Skip to content

Update stacklok/toolhive-studio to v0.37.0#1020

Merged
samuv merged 1 commit into
mainfrom
renovate/stacklok-toolhive-studio-0.x
Jul 8, 2026
Merged

Update stacklok/toolhive-studio to v0.37.0#1020
samuv merged 1 commit into
mainfrom
renovate/stacklok-toolhive-studio-0.x

Conversation

@renovate

@renovate renovate Bot commented Jul 7, 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.36.7 → v0.37.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.37.0

Compare Source

What's Changed

New Contributors

Full Changelog: stacklok/toolhive-studio@v0.36.7...v0.37.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.37.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.36.7 → v0.37.0
Hand-written changes 0 commit(s)
Reference assets unchanged
Gaps 1
Release contributors 4 auto-assigned (see sidebar)
Action required Yes — resolve 1 gap(s), then spot-check prose

Gaps needing human context

Color scheme customization (PR stacklok/toolhive-studio#2263 by @kantord)

Studio v0.37.0 introduces a user-level design-token override: on launch, the app
reads <userData>/branding-0.json (or the path in the BRANDING_CONFIG_PATH
env var) and, if present, replaces the default color tokens with the JSON's
design_tokens.colors.{light,dark} maps. There is no in-app UI for this; the
only way to configure it is to write the JSON file to a platform-specific path.
The PR body explicitly defers a docs-site write-up:
"documentation site updates on this feature (would make more sense after better
unification across code bases)." The schema in common/branding/schema.ts
also declares app_name, logo_url, and favicon_url fields that are
"parsed for forward compatibility but not yet applied," so any user-facing
guide today would need to explicitly scope readers to color overrides only.
A human reviewer should decide whether to publish a minimal reference now
(covering the file path, the color-token schema, and the restart-to-apply
behavior) or hold until the broader unification lands.

File(s): new page under docs/toolhive/guides-ui/ (e.g.,
customize-appearance.mdx), plus a sidebar entry and a cross-link from
docs/toolhive/guides-ui/install.mdx (which currently only mentions the
built-in light/dark theme setting).

Helper prompt for local Claude:

Read stacklok/toolhive-studio#2263 and the source at tag v0.37.0:
common/branding/schema.ts, common/branding/color-tokens.ts,
main/src/branding/load.ts, main/src/branding/paths.ts, and
branding-examples/README.md. The author (@kantord) deferred docs pending
token unification across codebases, but agree with the reviewer on whether
to ship a minimal user-facing reference now. If yes, write a new
docs/toolhive/guides-ui/customize-appearance.mdx covering: the exact per-OS
path for branding-0.json (Linux ~/.config/ToolHive/,
macOS ~/Library/Application Support/ToolHive/, Windows %APPDATA%/ToolHive/),
the BRANDING_CONFIG_PATH env var override, the design_tokens.colors
shape (light/dark color maps keyed by CSS custom property names), accepted
CSS color forms (#hex, hsl(...), oklch(...), etc. — bare HSL triplets
are rejected), and the "restart the app to apply changes" behavior. Scope
the page to color overrides only; explicitly note that app_name,
logo_url, and favicon_url are reserved but not yet applied. Add a
sidebar entry in sidebars.ts and a cross-link from
docs/toolhive/guides-ui/install.mdx (near the "Display theme" bullet) so
readers who set the built-in light/dark preference can discover the deeper
override.

Run cost

Session Turns Cost (USD)
Generation 47 $3.3285
Editorial review 5 $0.5174
Total 52 $3.8459
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.37.0
f3c7f33 
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 Jul 7, 2026
@vercel

vercel Bot commented Jul 7, 2026 •
edited
Loading

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
docs-website Ready Ready Preview, Comment Jul 7, 2026 7:00pm

Request Review

@github-actions github-actions Bot marked this pull request as draft July 7, 2026 18:59
@claude

claude Bot commented Jul 7, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

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

Upstream release docs: toolhive-studio v0.36.7 → v0.37.0

No hand-written docs changes required for this release.

Why: the v0.37.0 changelog is dominated by ~40 Renovate dependency bumps and CI-only PRs. The user-facing PRs are either bug fixes (stacklok/toolhive-studio#2398, stacklok/toolhive-studio#2425), internal migrations (stacklok/toolhive-studio#2368 AI SDK v7, stacklok/toolhive-studio#2440 playground model IDs — docs list providers, not model IDs), or minor UX polish (stacklok/toolhive-studio#2393 newsletter dismiss period — not documented). None of these introduce, change, or falsify any documented behavior; a displacement audit across guides-ui/ for theme, color scheme, branding, design token, downgrade, dismiss, newsletter, on-ramp, and provider names surfaced no contradictions.

One deferral, captured in GAPS.md: stacklok/toolhive-studio#2263 (color scheme customization by @kantord) introduces a JSON-file design-token override at <userData>/branding-0.json with no in-app GUI. The PR body explicitly defers docs-site updates pending token unification across codebases, and the schema declares several forward-compat fields (app_name, logo_url, favicon_url) that are "parsed but not yet applied." I've flagged this for a human reviewer to decide whether to ship a minimal reference now or hold.

  • Phase 1: Discovery
  • Phase 2: Deep dive
  • Phase 3: Docs audit — impact map empty; one deferred gap
  • Phase 4: Implementation — GAPS.md written; no hand-edits
  • Phase 5: Format & lint — nothing to lint
  • Phase 6: Commit & summarize — nothing to commit; no SUMMARY.md (zero hand-edits)
    · Branch

@claude

claude Bot commented Jul 7, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

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

Editorial review: toolhive-studio v0.37.0 upstream release

Nothing to review or edit.

What the previous session committed: the only file in HEAD is .github/upstream-projects.yaml (a version bump — not docs content). The prior session concluded that no hand-written docs changes were needed for v0.37.0 and left a GAPS.md signal file at the repo root for the next workflow step. Signal files (GAPS.md, NO_CHANGES.md, SUMMARY.md) are out of scope for editorial review per my instructions.

Verification:

  • git show --name-only HEAD → .github/upstream-projects.yaml only
  • git status → clean working tree
  • No .md/.mdx files under docs/ were modified in this commit

Since there are no docs changes in this PR, there is nothing to run /docs-review against, and nothing to format or lint.

  • Identify files changed in HEAD
  • Confirm no docs files require editorial review
  • Confirm signal files are out of scope
    · Branch

@github-actions github-actions Bot requested review from kantord and samuv July 7, 2026 19:06
@github-actions github-actions Bot marked this pull request as ready for review July 7, 2026 19:06
@kantord

kantord commented Jul 8, 2026

Copy link
Copy Markdown
Member

@claude we do not need to add user-facing documentation for the theme customization yet, as there is no clear use case for end users, currently it's only used to build different themes for different editions of the desktop app, so it's purely an internal build system

@claude

claude Bot commented Jul 8, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Claude finished @kantord's task in 25s —— View job

Theme customization docs - confirmed, no action needed

Thanks for the context, @kantord. Agreed - no user-facing documentation for the color scheme customization (stacklok/toolhive-studio#2263) is needed for this release.

Since it's purely an internal build-system mechanism for producing per-edition desktop app themes (with no clear end-user use case yet), documenting it now would only expose an internal detail without a supported user workflow. That matches the original deferral in the PR body, so I'm resolving that gap as won't document (internal only).

Nothing to change:

  • No GAPS.md or other signal files exist on the branch (working tree is clean).
  • The only file in this PR is the .github/upstream-projects.yaml version bump.

This PR is ready to merge as-is. If the feature later gains a user-facing configuration workflow, we can add a guide under docs/toolhive/guides-ui/ at that point.

  • Read trigger request
  • Check branch for gap/signal files
  • Confirm no docs changes required
    · Branch

@samuv samuv merged commit 307998c into main Jul 8, 2026
6 checks passed
@samuv samuv deleted the renovate/stacklok-toolhive-studio-0.x branch July 8, 2026 08:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@samuv samuv samuv approved these changes
@kantord kantord Awaiting requested review from kantord

Assignees

No one assigned

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.

2 participants

@kantord @samuv