Skip to content

fix(ci): auto-release never detects feat/fix once the log exceeds the pipe buffer #556

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Weegy merged 1 commit into from
Jul 31, 2026
Merged

fix(ci): auto-release never detects feat/fix once the log exceeds the pipe buffer #556

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 19 additions & 6 deletions .github/workflows/auto-release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,20 +67,33 @@ jobs:
if [ -z "$latest" ]; then latest="v0.0.0"; range="HEAD"; else range="${latest}..HEAD"; fi
echo "latest tag: $latest (range: $range)"

msgs=$(git log --no-merges --pretty=format:'%s%n%b' $range)
# Write the log to a file rather than piping it into `grep -q`.
# `grep -q` exits at the first match, so a pipe writer that still has
# data buffered gets EPIPE — and under `set -o pipefail` that failed
# writer, not grep's 0, becomes the pipeline's status. The condition
# then reads as "no match" precisely BECAUSE there was a match. It only
# bites once the log exceeds the 64 KiB pipe buffer, so the release
# workflow worked until enough commits accumulated and then wedged
# permanently: no release -> no new tag -> a longer range next time.
# See v0.56.0 (2026-06-30) .. v0.57.0. grep reading a file cannot EPIPE.
msgs=$(mktemp)
git log --no-merges --pretty=format:'%s%n%b' $range > "$msgs"

bump=""
if printf '%s\n' "$msgs" | grep -qE 'BREAKING CHANGE' \
|| printf '%s\n' "$msgs" | grep -qE '^[a-z]+(\(.+\))?!:'; then
if grep -qE 'BREAKING CHANGE' "$msgs" \
|| grep -qE '^[a-z]+(\(.+\))?!:' "$msgs"; then
bump="minor" # pre-1.0: breaking -> minor
elif printf '%s\n' "$msgs" | grep -qE '^feat(\(.+\))?:'; then
elif grep -qE '^feat(\(.+\))?:' "$msgs"; then
bump="minor"
elif printf '%s\n' "$msgs" | grep -qE '^fix(\(.+\))?:'; then
elif grep -qE '^fix(\(.+\))?:' "$msgs"; then
bump="patch"
fi

if [ -z "$bump" ]; then
echo "No feat/fix commits since $latest — skipping release."
# Print the range size too: "0 commits" is a normal skip, whereas
# "no feat/fix among N commits" for a large N is the signature of a
# detection bug and should be visible in the log, not silent.
echo "No feat/fix commits among $(git rev-list --no-merges --count $range) commit(s) since $latest — skipping release."
exit 0
fi

Expand Down
Loading