Conversation
beta.yml and release-assets.yml end by sending repository_dispatch `ftw-release` to srcfl/home-assistant-addons, whose sync already listens for it and otherwise polls hourly. The step uses HA_ADDON_DISPATCH_TOKEN and logs a notice when the secret is absent, so a release is never blocked by the app repository. AGENTS.md records the secret as repository setup. Part of srcfl#1233. Co-authored-by: HuggeK <48095810+HuggeK@users.noreply.github.com> Claude-Session: https://claude.ai/code/session_014Mn3h7AgWsYcNgPGSCBU62
This was referenced Sep 13, 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
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.
Part of #1233. Companion: srcfl/home-assistant-addons#8 rebuilds the app repository so it can consume these events.
beta.ymlandrelease-assets.ymlgain a final job that sendsrepository_dispatchftw-releaseto srcfl/home-assistant-addons once the release and its digest receipt exist. That repository'ssync-upstream.ymlalready listens for this event type; today it only polls hourly, and its build is broken by #1083.The job uses a new secret,
HA_ADDON_DISPATCH_TOKEN. When it is unset the job logs a notice and succeeds, so this can merge before the secret exists and a release is never blocked by the app repository.Secret setup (owner)
srcfl/home-assistant-addonsonly.repository_dispatchneeds write access to the target repository, and the job-scopedGITHUB_TOKENcannot reach another repository.HA_ADDON_DISPATCH_TOKENunder Settings → Secrets and variables → Actions insrcfl/ftw.LEGACY_GHCR_TOKEN. AGENTS.md gets one paragraph saying so.What the app repository does with the event
The payload (
channel,tag,commit, plussource_betafor stable) is informational. The receiving sync reads FTW's GitHub releases, downloadsftw-image-digests.json(beta) orftw-promotion-receipt.json(stable), and checks the Core image digest and OCI labels in the registry before pinning anything. A forged or wrong payload cannot make it publish a different image.Validation: CI-only change plus a Markdown paragraph, so no changeset (allowlisted). The dispatch has not run end to end because it needs the secret in
srcfl/ftw; the call is the documentedPOST /repos/{owner}/{repo}/dispatchesform viagh api, and the receiving repository's tests cover the event type.🤖 Generated with Claude Code
https://claude.ai/code/session_014Mn3h7AgWsYcNgPGSCBU62