ci: notify downstream on core PyPI publish#142
Merged
Conversation
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.
Summary
notify-downstreamjob torelease-core.ymlthat fires after a successful PyPI publishcore-releasedrepository_dispatchevent tolongieirl/bankstatementswith the new core version, SHA, and run URL in the payloadcore-release-sync.ymlworkflow receives this, runs tests, bumps the premium version + core pin, commits, and tags — which triggersrelease.ymlto build and push the Docker image automaticallySecrets required
DOWNSTREAM_DISPATCH_TOKENmust be set in this repo's secrets — fine-grained PAT scoped tolongieirl/bankstatementswithContents: writeTest plan
core-vX.Y.Zrelease and verifynotify-downstreamjob fires and dispatches to the private repo