ci: notify downstream repos on release - #59
Merged
Conversation
This was referenced Jul 22, 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.
Adds a
notify-downstreamjob that fires arepository_dispatch(event typefirst-party-release) to downstream repos when@comapeo/map-serverpublishes, so they fast-track the dependency bump instead of waiting for their daily Dependabot run.Pairs with the receiver workflow in digidem/comapeo-core-react-native#173. The downstream destinations are a matrix (
owner/repo), so adding more later is a one-line change.Requires:
RELEASE_BOT_APP_ID+RELEASE_BOT_PRIVATE_KEYavailable to this repo, and the Releases bot installed on each downstream repo with Contents: write (needed to send the dispatch).