feat(summary): pushed/reason/repositories fields + summary step output#9
Merged
Conversation
Closes #6. CI consuming a release needs a structured record of what was actually published — pinpredict's docker-release.yml must notify its deploy correlator once per pushed image, and with stevedore deciding what builds, the workflow is otherwise blind. - summary.Image gains `repositories` (bare repos, no tag), `pushed` (false under --no-push validation builds — consumers filter on it), and `reason` (why it built, or why it was skipped). - The skipped rows of the job-summary table show the real skip reason instead of hardcoded "unchanged". - Under GitHub Actions, emitSummary also writes the compact JSON as a `summary` step output ($GITHUB_OUTPUT), republished by the composite action — no dist-path knowledge or jq parsing needed in workflows. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
blairham
added a commit
to pinpredict/.github
that referenced
this pull request
Jul 5, 2026
…dore summary (#41) * feat(docker-release): notify Dispatch per pushed image from the release summary Closes the one behavior gap vs the matrix implementation. stevedore v0.0.6 (blairham/stevedore#9) emits the release summary as a `summary` step output; a jq step filters it to pushed images (no-push validation builds and skipped images notify nothing) and hands the batch to notify-dispatch, which gains a `batch` JSON-array mode alongside the existing single-artifact inputs. With parity restored, `no-push` now defaults false. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * feat(docker-release): only input for explicit image selection Maps to stevedore release --only <csv>, bypassing change detection for the selected ids. Lets callers keep their workflow_dispatch service pickers (e.g. trading's services: input) across the migration. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <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.
Closes #6.
Motivation: pinpredict/.github#39 —
docker-release.yml(now stevedore-backed) must callnotify-dispatchonce per pushed image; the workflow needs a machine-readable record of what the release actually did.summary.Imagegainsrepositories(bare repos),pushed(false under--no-push— the filter consumers key off), andreason(populated for both built and skipped images from change detection).emitSummarywrites the compact JSON as asummarystep output when$GITHUB_OUTPUTis set;action.ymlrepublishes it as thesummaryoutput. Works regardless of a customdistpath, no stdout parsing.GITHUB_OUTPUTround-trip (single line, fields survive), no-op outside Actions.make checkgreen; actionlint clean.Group members each keep their own entry (own version/repos/reason) even when built once, per the issue.
🤖 Generated with Claude Code