From 30b2b0f939d412c071a2eb7045335f76680fbf84 Mon Sep 17 00:00:00 2001 From: cedricroulof Date: Sun, 8 Nov 2026 17:52:59 +0100 Subject: [PATCH] chore(ci): notify coretrace-runner when a release is published 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. --- .github/workflows/release.yml | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index fa52165..953192c 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -41,3 +41,19 @@ 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