From a8c86eee2e00740f2847250cd782658bc47b007d Mon Sep 17 00:00:00 2001 From: Santiago Date: Wed, 26 Aug 2026 12:48:41 -0300 Subject: [PATCH] ci: allow CI to be triggered on demand MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit GitHub disables re-running a workflow run once it is older than 30 days, and both jobs run `poetry lock` against live PyPI rather than the committed lockfile. Together that means there is no way to check whether the toolchain has drifted since the last push — the only signal is a release tag, which publishes. `workflow_dispatch` makes CI re-runnable at any time. The release pipeline is untouched: it stays tag-only, as the umbrella contract requires. Co-Authored-By: Claude Opus 5 (1M context) --- .github/workflows/ci.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index a361226..cc8012c 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -4,6 +4,9 @@ on: branches: [main] push: branches: [main] + # On-demand trigger: GitHub refuses to re-run a run older than 30 days, and + # both jobs relock against live PyPI, so drift is only observable on a fresh run. + workflow_dispatch: jobs: build: