From ee3469c2e2c6430f7e008e426efe5ce616d95f3f Mon Sep 17 00:00:00 2001 From: Daniel Rossier Date: Mon, 10 Aug 2026 18:56:45 +0200 Subject: [PATCH] ci: run Build and Style on the release branches too MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Both workflows only triggered on main, yet tags are cut on release/vX.Y — the very commits a release points at were the only ones never built. Add release/** to the push and pull_request triggers so a patch release is validated before it is tagged, and document the pre-tag check in release_process.rst (the Docs workflow already runs on every ref). --- .github/workflows/build.yml | 3 ++- .github/workflows/style.yml | 4 ++-- doc/source/release_process.rst | 14 ++++++++++++++ 3 files changed, 18 insertions(+), 3 deletions(-) diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index d8aa3b9a84..4551a110b1 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -4,8 +4,9 @@ on: push: branches: - main + - "release/**" pull_request: - branches: ["main"] + branches: ["main", "release/**"] # Smoke-build SO3 with Infrabase (bitbake) inside the so3-env image. Both the # kernel (build.sh -x so3) and the user space (build.sh -x usr-so3, which also diff --git a/.github/workflows/style.yml b/.github/workflows/style.yml index 94a9d373fb..3d64bb9361 100644 --- a/.github/workflows/style.yml +++ b/.github/workflows/style.yml @@ -8,9 +8,9 @@ concurrency: on: push: - branches: ["main"] + branches: ["main", "release/**"] pull_request: - branches: ["main"] + branches: ["main", "release/**"] jobs: formatting-check: diff --git a/doc/source/release_process.rst b/doc/source/release_process.rst index 3315387c2e..d37ed7174b 100644 --- a/doc/source/release_process.rst +++ b/doc/source/release_process.rst @@ -141,6 +141,20 @@ release (they drift silently otherwise): ``PREFERRED_VERSION_avz`` entries in ``build/conf/local.conf`` (see the ``v6.2.3`` bump for a template). +Before tagging: check the CI +*************************** + +The ``Build`` workflow runs on ``main`` **and on every** ``release/**`` +**branch**, so the commit a tag will point at has always been built. Check it +before tagging:: + + gh run list --workflow Build --branch release/v6.2 + +Tagging a red commit is how ``v6.2.4`` shipped a tree that no fresh clone +could build. ``build (virt32)`` and ``build (virt64)`` are required status +checks on ``main`` for the same reason: merging on red stays possible for a +maintainer, but never by accident. + Rules of thumb **************