From a6b7dbd229da2c99461e42cf1a09e9d9a2cda3d9 Mon Sep 17 00:00:00 2001 From: Dima Molodenskiy Date: Mon, 10 Aug 2026 15:54:07 +0200 Subject: [PATCH] Trigger CI on published releases so versioned Docker tags get pushed The docker job has a "Build and push : on release" step gated on github.event_name == 'release', but the workflow's on: block only listed push and pull_request. A workflow that is never triggered by a release event can never satisfy that condition, so the step has never run. Across the last 100 workflow runs the event breakdown is push 69, pull_request 31, release 0, while nine releases have been published (1.0.0 through 1.4.1). Docker Hub correspondingly carries a single tag: both the Hub API (count: 1) and the registry v2 tags/list return only ":latest", which is refreshed by the separate push-to-main step. Adding the release trigger is sufficient. The test job has no if: condition so it runs on release events, the docker job's existing if: already admits them, and coverage-pages stays gated on push-to-main. On a published release the PR-only and push-to-main steps skip and the release step pushes /alphajudge:. Note this is not retroactive: images for the already-published 1.0.0-1.4.1 releases would still need a manual build or a re-published release. Co-Authored-By: Claude Opus 5 --- .github/workflows/github_actions.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/workflows/github_actions.yml b/.github/workflows/github_actions.yml index 366631d3..69acc7eb 100644 --- a/.github/workflows/github_actions.yml +++ b/.github/workflows/github_actions.yml @@ -5,6 +5,8 @@ on: branches: [ "**" ] pull_request: branches: [ "**" ] + release: + types: [published] jobs: test: