The automated release workflow added by #216 fails on the normal untagged main path.
In .github/workflows/release.yml, EXACT_TAG is assigned from a grep pipeline while the shell is running with set -euo pipefail. When HEAD has no stable tag, grep exits 1 and terminates the step before the workflow can reach its skip handling or invoke next-release-version.sh. As a result, deployable untagged main commits cannot obtain a release version.
This was identified while syncing #216 into ClickHouse/ai: https://github.com/ClickHouse/ai/pull/3846#discussion_r4032462076
Suggested direction: make the no-match result non-fatal while preserving genuine command failures, and cover the untagged-HEAD path in the release workflow tests.
The automated release workflow added by #216 fails on the normal untagged
mainpath.In
.github/workflows/release.yml,EXACT_TAGis assigned from agreppipeline while the shell is running withset -euo pipefail. WhenHEADhas no stable tag,grepexits 1 and terminates the step before the workflow can reach its skip handling or invokenext-release-version.sh. As a result, deployable untaggedmaincommits cannot obtain a release version.This was identified while syncing #216 into ClickHouse/ai: https://github.com/ClickHouse/ai/pull/3846#discussion_r4032462076
Suggested direction: make the no-match result non-fatal while preserving genuine command failures, and cover the untagged-HEAD path in the release workflow tests.