Notify release-automation on release via repository_dispatch - #469
Closed
boddumanohar wants to merge 1 commit into
Closed
boddumanohar wants to merge 1 commit into
boddumanohar wants to merge 1 commit into
Conversation
release-automation's certified/community-operators workflows were listening for a workflow_run named "Release" — a trigger that can only observe workflows in the same repository, and no such workflow exists there or here. Those pipelines have never fired. Fire an explicit repository_dispatch with the release tag once the bundle is uploaded, matching the trigger release-automation now listens for. Needs a RELEASE_AUTOMATION_DISPATCH_TOKEN secret (a token with write access to simplyblock/release-automation) added to this repo.
noctarius
force-pushed
the
main
branch
2 times, most recently
from
September 9, 2026 10:21
60dceb7 to
fbaabe4
Compare
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
release-automation'scertified-operators.yml/community-operators.ymlwere listening for aworkflow_runnamedRelease. That trigger only observes workflows in the same repository, and no workflow namedReleaseexists in either repo — confirmed viagh run listthat these pipelines have never run, ever.operator_release.yamlthat fires arepository_dispatch(event_type: operator-release,client_payload.tag) tosimplyblock/release-automationonce the OLM bundle is uploaded to the GitHub release.repository_dispatchinstead, and fixes a couple of bugs found during the same review (bundle download was reading from the wrong repo, the version regex rejected real-rc-suffixed releases and silently miscomputedreplacesfor them, and retries weren't idempotent).Requires
RELEASE_AUTOMATION_DISPATCH_TOKENsecret in this repo — a token with write access tosimplyblock/release-automation(private repo), since the defaultGITHUB_TOKENhere is scoped to this repo only.Test plan
actionlint .github/workflows/operator_release.yaml— clean.RELEASE_AUTOMATION_DISPATCH_TOKENis added, then confirm a real (or manually re-run) release actually triggers therelease-automationworkflow end to end.