Update toolhive to v0.23.1 (manual dispatch)#777
Closed
github-actions[bot] wants to merge 1 commit intoe2e-test-upstream-release-docsfrom
Closed
Update toolhive to v0.23.1 (manual dispatch)#777github-actions[bot] wants to merge 1 commit intoe2e-test-upstream-release-docsfrom
github-actions[bot] wants to merge 1 commit intoe2e-test-upstream-release-docsfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
requested review from
ChrisJBurns,
jhrozek,
rdimitrov,
reyortiz3 and
tgrunnagle
rdimitrov
added a commit
that referenced
this pull request
Apr 22, 2026
Companion to the tracking comments: when the skill concludes
successfully but produces zero commits, the PR body previously
read as if content was added. Reviewers had no way to distinguish
"skill ran silently" from "skill produced stuff".
Adds:
- A new step that rev-counts commits between pre_skill SHA and
HEAD. Output exposed as steps.skill_commits.outputs.count.
- A [!NOTE] block in the PR body when SKILL_COMMIT_COUNT=0 and
no NO_CHANGES.md was written. Lists the three likely causes
(docs already ahead of pin; no doc-relevant release; skill's
verification matched existing prose).
- A row in the workflow_dispatch summary comment showing the
commit count.
Surfaced by the e2e test on PR #777: the skill ran to success but
produced nothing because main was already ahead of the pinned
scratch branch. PR body looked like a normal augmented PR.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
rdimitrov
added a commit
that referenced
this pull request
Apr 22, 2026
* Add skill-started + skill-completed PR comments for workflow_dispatch
claude-code-action@v1 rejects track_progress: true on
workflow_dispatch events, so manual retries and bootstrap
dispatches leave no real-time signal on the PR that the skill is
running -- reviewers had to hunt through the Actions tab to see
progress. On pull_request runs the action posts its own tracking
comment, so this gap only affects workflow_dispatch.
Two workflow_dispatch-only comments:
- Before skill_gen: a "Claude Opus is generating docs updates for
<project> <tag>. Follow progress: <run URL>" placeholder. Static
but enough to signal "yes it started".
- After Augment PR body: a run summary with skill_gen /
skill_review / autofix conclusions and a link to the run for
the Claude Code Report. Runs even if earlier steps failed so
reviewers can see which step died.
Both are gated on `github.event_name == 'workflow_dispatch'` to
avoid duplicating the action's own tracking on Renovate-opened PRs.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* Flag silent skill runs in PR body + dispatch summary
Companion to the tracking comments: when the skill concludes
successfully but produces zero commits, the PR body previously
read as if content was added. Reviewers had no way to distinguish
"skill ran silently" from "skill produced stuff".
Adds:
- A new step that rev-counts commits between pre_skill SHA and
HEAD. Output exposed as steps.skill_commits.outputs.count.
- A [!NOTE] block in the PR body when SKILL_COMMIT_COUNT=0 and
no NO_CHANGES.md was written. Lists the three likely causes
(docs already ahead of pin; no doc-relevant release; skill's
verification matched existing prose).
- A row in the workflow_dispatch summary comment showing the
commit count.
Surfaced by the e2e test on PR #777: the skill ran to success but
produced nothing because main was already ahead of the pinned
scratch branch. PR body looked like a normal augmented PR.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* Address Copilot review feedback on #778
Two fixes from Copilot's line-level comments:
1. Pre-skill placeholder comment step is best-effort. Was previously
unguarded -- a transient gh failure (rate limit, API hiccup,
permission edge case) would abort the workflow before skill_gen
ran. Matches the `|| true` pattern already used by the post-run
summary comment and the augmentation-failure comment.
2. Silent-run [!NOTE] is gated on BOTH skill steps having succeeded.
The note claims "ran to success"; previously the condition only
checked SKILL_COMMIT_COUNT=0 and NOTE_BLOCK empty, which could
trigger the note even if skill_review had failed. Now requires
steps.skill_gen.conclusion == 'success' AND
steps.skill_review.conclusion == 'success'. Partial failures
are already covered by the separate augmentation-failure
comment step.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Manually dispatched by @rdimitrov via workflow run https://github.com/stacklok/docs-website/actions/runs/24767008554.
This PR was created by the
Upstream Release Docsworkflow'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/toolhiveat tagv0.23.1(wasv0.22.0). Two Claude Opus sessions produced this update: a generation pass running theupstream-release-docsskill over all six phases, then a fresh-context editorial pass runningdocs-reviewover the changed files. Prettier and ESLint auto-fixes were applied afterward.Review guidance
Machine-generated reference files under
docs/toolhive/reference/cli/,static/api-specs/, anddocs/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