Repository navigation
chore(ci): notify coretrace-runner when a release is published - #292
Merged
Merged
Conversation
The platform pins this package by version in coretrace-runner. A dispatch after the PyPI publish lets that repository resolve the new version and open its own pull request for the bump, instead of the pin drifting until someone notices. Best effort: the step is continue-on-error and no-ops when RUNNER_DISPATCH_TOKEN is absent, so it can never fail a release.
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.
Adds one step at the end of the existing
publishjob: after the PyPI publish succeeds, it notifies a downstream build pipeline that a new release is available, so that pipeline can pick the version up rather than waiting for a manual update.continue-on-error, and it no-ops when its secret is not configured, so it cannot fail a release.