Repository navigation
Version check: workflow build steps and a no-release label #239
Description
.github/check-version.sh requires a new version when the sources or the build scripts change, but not for .github/workflows/. A workflow edit that changes the build itself (compiler flags, a toolchain, a build step) changes the released files without a new version, and the release keeps the old title.
Proposal:
- Count the build steps of the workflow as build: a change to them needs a new version like a change to
ci/or the Makefile; the rest of.github/stays CI and needs none. - Add the
no-releaselabel as in ci: a no-release label lets a change that keeps the binaries skip the version; review follow-ups cerberus#39: a change to the code or the build that leaves the binaries as they are (a script tidy-up, a comment) passes the check without a new version.
Decision needed: both, only 1, only 2, or neither.
Activity
compot-dev commentedon Oct 18, 2026
Decision: both. Build steps in the workflow count as build and need a new version; the
no-releaselabel lets a change that keeps the release files as they are pass without one. Next: the check and the label in this repository.docs: testing.md — the build workflow needs a new version or the no-r…
Merge pull request #241 from OpenIPC/version-check-workflow