Skip to content

Update toolhive to v0.23.1 (manual dispatch)#779

Closed
github-actions[bot] wants to merge 1 commit intoe2e-test-v2from
manual/upstream-toolhive-v0.23.1
Closed

Update toolhive to v0.23.1 (manual dispatch)#779
github-actions[bot] wants to merge 1 commit intoe2e-test-v2from
manual/upstream-toolhive-v0.23.1

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented Apr 22, 2026

Manually dispatched by @rdimitrov via workflow run https://github.com/stacklok/docs-website/actions/runs/24769137629.

This PR was created by the Upstream Release Docs workflow's bootstrap mode to document a release without waiting for Renovate. Content edits will be pushed as additional commits by the same workflow run.


Content additions by upstream-release-docs

Source-verified against stacklok/toolhive at tag v0.23.1 (was v0.22.0). Two Claude Opus sessions produced this update: a generation pass running the upstream-release-docs skill over all six phases, then a fresh-context editorial pass running docs-review over the changed files. Prettier and ESLint auto-fixes were applied afterward.

Note

The upstream-release-docs skill ran to success but
produced no content commits on this PR. Likely causes:

  • The docs already cover this release (e.g. this PR
    was dispatched after an earlier PR for the same
    tag had merged, or main is already ahead of the
    pinned base).
  • The release genuinely had no doc-relevant changes
    but the skill did not write NO_CHANGES.md (which
    would have triggered the standard 'no changes'
    note above).
  • The skill's source verification concluded the
    existing prose already matches upstream behavior.

Only the version bump and any refreshed reference
assets are included in this PR.

Review guidance

Machine-generated reference files under docs/toolhive/reference/cli/, static/api-specs/, and docs/toolhive/reference/crds/ are synced or regenerated from upstream release assets (separate commit, titled "Refresh reference assets") and should be spot-checked only. Commits authored by the skill contain hand-edited prose; review those for accuracy, not just style. If the "Gaps needing human context" section below is populated, each entry includes a Helper prompt for local Claude that a reviewer can paste verbatim into their local Claude Code session to resolve the gap. Fill those in before merging.

Release contributors

Auto-assigned as reviewers (collaborators on this repo): @ChrisJBurns @jhrozek @rdimitrov @reyortiz3 @tgrunnagle

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 22, 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 22, 2026 8:48am

Request Review

@github-actions
Copy link
Copy Markdown
Contributor Author

Claude Opus is generating docs updates for toolhive v0.23.1. Follow progress in the workflow run: https://github.com/stacklok/docs-website/actions/runs/24769137629

(This comment replaces the real-time tracking comment claude-code-action posts on Renovate-opened PRs, which isn't supported on workflow_dispatch events.)

@github-actions
Copy link
Copy Markdown
Contributor Author

Upstream-release-docs run summary

Project: toolhive at tag v0.23.1

Step Conclusion
Generation (skill_gen) success
Editorial review (skill_review) success
Autofix (prettier/eslint) success
Skill commits produced 0

Full report and Claude's step-by-step log: https://github.com/stacklok/docs-website/actions/runs/24769137629

@rdimitrov rdimitrov closed this Apr 22, 2026
@rdimitrov rdimitrov deleted the manual/upstream-toolhive-v0.23.1 branch April 22, 2026 08:55
rdimitrov added a commit that referenced this pull request Apr 22, 2026
* Record per-skill turns/cost and surface in PR body + summary

Adds two capture steps that parse claude-code-action's execution
log (`/home/runner/work/_temp/claude-execution-output.json`) right
after each skill invocation, BEFORE the next one overwrites the
shared file. Exposes `turns`, `cost_usd`, and `permission_denials`
as step outputs for downstream use.

Surfaces the data in two places:

1. PR body: new "Run cost" subsection inside the upstream-release-
   docs marker block. Per-session rows plus a Total row when both
   sessions reported. Applies to both pull_request and
   workflow_dispatch runs.

2. workflow_dispatch summary comment: adds Turns and Cost columns
   to the existing step table, plus a Total row summing both
   sessions.

Useful for tracking per-release spend ($6 baseline) and catching
regressions -- e.g. a release that suddenly takes 10x the turns is
visible at a glance rather than requiring a drill-down into the
Actions Step Summary.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Reorganise PR body and comments for scannability

Ground-up redesign of everything the workflow posts on a PR.
Previous output read as three authors writing on the same page
(log formatter + release notes + systems docs), with no visual
hierarchy and a lot of process lore competing with actionable
info. Feedback after PRs #779 and #780.

Key structural shift: the PR body is the single source of truth
for state. Comments are point-in-time events only. Process lore
goes behind <details>.

Changes:

**PR body** (rewritten end-to-end)
- New H2: "Docs update for <project> <tag>" replaces the
  process-descriptive "Content additions by upstream-release-docs".
- New "At a glance" table with 6 rows: Upstream (linked compare),
  Hand-written changes, Reference assets, Gaps, Release
  contributors, Action required. Answers the 5 questions a
  reviewer actually asks in < 5 seconds.
- Single top-of-section alert (at most one), ordered by severity:
  CAUTION for autogen-path drift, NOTE for NO_CHANGES.md, NOTE
  for silent run. Never stacked.
- Autogen drift promoted from inline [!WARNING] paragraph to
  [!CAUTION] at the top with a bulleted revert list -- it's a
  merge-blocker, should look like one.
- "Review guidance" paragraph deleted. The one operational claim
  ("reference files are auto-synced") is in the At-a-glance
  "Reference assets" row.
- "Release contributors" section dropped when everyone got
  auto-assigned (GitHub's sidebar already shows them). Only
  rendered as "Additional release contributors" when overflow
  @-mentions need a target.
- "Run cost" table kept visible, not buried in <details>, per
  request.
- Process narrative ("Two Claude Opus sessions...", auto-synced
  paths, Helper-prompt convention) collapsed into a single
  <details> block at the bottom.
- Compare-failure warning moved from a top-of-section [!WARNING]
  block into the At-a-glance "Release contributors" cell.

**Bootstrap PR body**
- Collapsed from two paragraphs to one line ("Manually dispatched
  by @x. Workflow run: ..."). Mechanism narration deleted.

**Pre-skill placeholder comment** (workflow_dispatch only)
- From a two-paragraph explanation + parenthetical meta-note
  ("this comment exists because track_progress isn't supported
  on workflow_dispatch") to a single line: "Generating docs for
  <project> <tag>... (run)".

**Post-skill summary comment** (workflow_dispatch only)
- Table replaced with a one-line status: "Done · 93 turns · $6.04
  · run · see PR body for details". On failure, identifies which
  step died. Duplicative detail (conclusions, commit counts) was
  already in the PR body.
- Dropped "Skill commits produced" row -- the at-a-glance
  "Hand-written changes" cell covers it.

**Augmentation failure comment**
- Wrapped in [!CAUTION] alert, compressed to two lines with the
  exact retry gh command inline (not a hand-wavy "retry via the
  workflow" pointer).

**Autogen-touch step (`detect-autogen`)**
- Now emits `touched` output (comma-separated paths) directly
  instead of pre-formatting a warning block. The Augment step
  composes the alert itself. Cleaner separation of concerns.

Unchanged: reviewer assignment logic, skill prompts, autofix
step, concurrency config.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant