Add release event dispatcher workflow#2650
Open
mattdholloway wants to merge 1 commit into
Open
Conversation
Adds an opt-in workflow that fires repository_dispatch on release events
to a downstream repository, when one is configured via the
RELEASE_AUTOMATION_REPO repository variable. When the variable is unset,
the workflow is a no-op so forks and other adopters pay no overhead.
Two event types are emitted:
mcp-server-release-drafted on release: { types: [created] }
mcp-server-released on release: { types: [published] }
Prereleases are skipped for both event types. The downstream payload is
{ tag, url } only — no other release data crosses the boundary.
Required when RELEASE_AUTOMATION_REPO is set:
Variable RELEASE_AUTOMATION_REPO owner/repo of the downstream
Secret RELEASE_AUTOMATION_DISPATCH_PAT PAT with actions:write on it
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a GitHub Actions workflow to optionally forward release lifecycle events from this repository to a downstream repository via repository_dispatch, controlled by a repository variable so the default behavior is a no-op.
Changes:
- Introduces
release-triggered workflow that mapscreated→mcp-server-release-draftedandpublished→mcp-server-released. - Skips prereleases and sends only
{ tag, url }inclient_payload. - Gates the entire job on
vars.RELEASE_AUTOMATION_REPObeing set, and fails with a clear error if the PAT secret is missing when opted-in.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/release-dispatch.yml | Adds opt-in release event dispatching to a configured downstream repo using gh api and a PAT secret. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 0
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.
What
Adds an opt-in workflow that fires
repository_dispatchon release events to a downstream repository, when one is configured via theRELEASE_AUTOMATION_REPOrepository variable. When the variable is unset, the workflow is a no-op — so forks and other adopters pay no overhead unless they explicitly opt in.Event types emitted
release: { types: [created] }mcp-server-release-draftedprerelease == truerelease: { types: [published] }mcp-server-releasedprerelease == trueThe downstream payload is
{ tag, url }only — no other release data crosses the boundary.Required when opting in
RELEASE_AUTOMATION_REPOowner/repoof the downstream repositoryRELEASE_AUTOMATION_DISPATCH_PATactions: writeon that repoIf the variable is unset, the dispatch job is skipped with no action. If the variable is set but the secret is missing, the job fails with a clear error.
Why this exists
Allows release events from this repository to drive downstream automation (e.g. dependency bumps, downstream test runs, notifications) without coupling that automation's logic into this repository. The downstream repository owns its own behavior; this workflow just signals the event.
Testing
RELEASE_AUTOMATION_REPOunset: no-op confirmed (job'sif:evaluates false).mcp-server-releasedto the target repo, observable in that repo's Actions tab as arepository_dispatchevent.Concurrency
Scoped per
(release_id, action)so re-edits of the same release don't fan out.