Skip to content

Commit d1b2de4

Browse files
committed
Revert "chore(ci): notify coretrace-runner when a release is published"
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.
1 parent f833b1c commit d1b2de4

1 file changed

Lines changed: 0 additions & 16 deletions

File tree

‎.github/workflows/release.yml‎

Lines changed: 0 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -41,19 +41,3 @@ jobs:
4141
name: dist
4242
path: dist/
4343
- uses: pypa/gh-action-pypi-publish@release/v1
44-
45-
# Lets the platform repin itself: coretrace-runner re-resolves this package's newest
46-
# version on PyPI and opens a pull request for the bump, for both python-analyzer and
47-
# python-analyzer-pro. Best effort, and never fails the release: the pull request can
48-
# also be started by hand from that repository's Actions tab. The payload is a hint;
49-
# the version is resolved there, not taken from here.
50-
- name: Notify coretrace-runner of the release
51-
continue-on-error: true
52-
env:
53-
GH_TOKEN: ${{ secrets.RUNNER_DISPATCH_TOKEN }}
54-
run: |
55-
set -euo pipefail
56-
[ -n "${GH_TOKEN:-}" ] || { echo "no RUNNER_DISPATCH_TOKEN set, skipping"; exit 0; }
57-
gh api repos/CoreTrace-Entreprise/coretrace-runner/dispatches \
58-
-f event_type=tool-release \
59-
-F client_payload[tool]=python-analyzer

0 commit comments

Comments
 (0)