Repository navigation
Revert "chore(ci): notify coretrace-runner when a release is published" - #293
Merged
Merged
Conversation
This reverts commit 30b2b0f, merged as #292. Dependency monitoring belongs in the consuming repository, not in a dispatch from the producer: coretrace-runner polls this package's releases on a schedule instead, so this repository does not need to know it has a consumer and no cross-repository RUNNER_DISPATCH_TOKEN is required. The equivalent change in coretrace-stack-analyzer (#269) was closed for the same reason; this keeps the two release pipelines consistent.
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.
Reverts #292 (commit
30b2b0f). −16 lines, nothing added. No package code is touched; this removes the notification step from thepublishjob and restores.github/workflows/release.ymlto its pre-#292 state byte for byte.Why
The equivalent change in
coretrace-stack-analyzer(#269) was closed on the grounds that dependency monitoring belongs in the consuming repository rather than in a notification from the producer. That reasoning applies identically here, and the argument is right:Leaving #292 merged while #269 is closed would also leave the two release pipelines inconsistent.
What replaces it
Nothing in this repository. Consumers poll this package's releases on their own schedule, which is the usual model for dependency updates.