Skip to content

ci: run Build and Style on the release branches too - #314

Merged
daniel-rossier merged 1 commit into
mainfrom
feat/ci-release-branches
Aug 10, 2026
Merged

ci: run Build and Style on the release branches too#314
daniel-rossier merged 1 commit into
mainfrom
feat/ci-release-branches

Conversation

@daniel-rossier

Copy link
Copy Markdown
Contributor

Both workflows only triggered on main, yet tags are cut on release/vX.Y — so the very commits a release points at were the only ones never built. That is the structural half of how v6.2.4 shipped a tree no fresh clone could build (the other half, the materialized lvgl files, is fixed by #313).

  • build.yml / style.yml: add release/** to the push and pull_request triggers (Docs already runs on every ref).
  • release_process.rst: a short "Before tagging: check the CI" section, pointing at gh run list --workflow Build --branch release/v6.2, and noting that build (virt32)/build (virt64) are now required status checks on main.

Prerequisite for cutting v6.2.5 on release/v6.2 with CI validation.

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).
@daniel-rossier
daniel-rossier merged commit 3483d39 into main Aug 10, 2026
8 of 10 checks passed
@daniel-rossier
daniel-rossier deleted the feat/ci-release-branches branch August 10, 2026 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant