From d1b2de45ce5e65201226dfd10a3a5c691aabaeef Mon Sep 17 00:00:00 2001 From: cedricroulof Date: Sun, 8 Nov 2026 18:23:16 +0100 Subject: [PATCH] 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. --- .github/workflows/release.yml | 16 ---------------- 1 file changed, 16 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 953192c..fa52165 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -41,19 +41,3 @@ jobs: name: dist path: dist/ - uses: pypa/gh-action-pypi-publish@release/v1 - - # Lets the platform repin itself: coretrace-runner re-resolves this package's newest - # version on PyPI and opens a pull request for the bump, for both python-analyzer and - # python-analyzer-pro. Best effort, and never fails the release: the pull request can - # also be started by hand from that repository's Actions tab. The payload is a hint; - # the version is resolved there, not taken from here. - - name: Notify coretrace-runner of the release - continue-on-error: true - env: - GH_TOKEN: ${{ secrets.RUNNER_DISPATCH_TOKEN }} - run: | - set -euo pipefail - [ -n "${GH_TOKEN:-}" ] || { echo "no RUNNER_DISPATCH_TOKEN set, skipping"; exit 0; } - gh api repos/CoreTrace-Entreprise/coretrace-runner/dispatches \ - -f event_type=tool-release \ - -F client_payload[tool]=python-analyzer