feat(release): notify Dispatch directly on publish + chart sha alias - #24
Merged
Conversation
Dispatch learns about published artifacts from the create-webhook on the legacy image/*+chart/* git tags; those stop being minted at the end of platform-gitops#1201, so the release workflows now emit the replacement signals themselves. A shared notify-dispatch composite POSTs a signed publish notification (service, version, full commit SHA, run URL) through the public /dispatch/ci route after each successful push — warn-only, since the EventBridge ECR-push backstop covers a missed call. chart-release additionally aliases the pushed OCI chart as X.Y.Z-<sha7> (put-image on the same manifest, allowed under tag immutability) so that backstop can recover chart commit provenance the way it already does for images; the prerelease-shaped tag is invisible to Kargo's chart Warehouses. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 2, 2026
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.
Summary
PR 4 of the platform-gitops#1201 sequence — the release workflows emit the signals that replace the
image/*/chart/*git-tag webhook:actions/notify-dispatchcomposite: signed POST ({repo, kind, service, version, sha, run_url}, hex HMAC inX-Dispatch-Signatureusing the orgCI_WEBHOOK_SECRETviasecrets: inherit) through the public webhook-forwarder/dispatch/ciroute. Called by both release workflows after each successful push. Warn-only on every failure mode (missing secret, non-2xx, network) — a release never fails on a notification; the EventBridge ECR-push backstop covers a miss.X.Y.Z-<sha7>OCI alias in chart-release (aws ecr batch-get-image+put-imageon the just-pushed manifest): gives the ECR-push backstop commit provenance for charts, mirroring the image tag pair. Tag immutability allows aliasing (new tag, same manifest); the push role already grants both actions oncharts/<name>; the prerelease-shaped tag is excluded by Kargo's semver chart subscriptions — same reason image-sha7tags never promote.Test plan
actionlintcleanprintf | openssl dgst -hmac | awkchain with the real SSM secret → dispatch returns400 invalid payloadon an intentionally-boguskind(signature accepted, payload rejected) vs401unsigned@main): dispatch an understudy release and confirm dispatch logsci release notification received+ publish slot filled by the CI path, andcharts/understudy:<ver>-<sha7>appears in ECR🤖 Generated with Claude Code