fix(ci): prevent release-drift and auto-release pipeline SIGPIPE/EPIP... - #1173

close:#990

Summary

Fixes a recurring failure where the Release drift check (release-drift.yml) and Auto Release (auto-release.yml) workflows fail with grep: write error: Broken pipe (exit code 2 / 141).

Root Cause

Both workflows utilized short-circuiting pipelines to get the latest tag:

• release-drift.yml: git tag --merged origin/main --sort=-v:refname | grep -E '^v[0-9]' | head -n1
• auto-release.yml: git tag --sort=-v:refname | grep '^v' | head -1

Under set -o pipefail (explicitly or via GitHub Actions' default shell configuration), head exits immediately after printing the first line and closes its side of the pipe. When the preceding grep tries to write subsequent lines to the closed pipe, it receives a SIGPIPE / EPIPE.

Because GitHub Actions runners often inherit SIG_IGN on SIGPIPE, grep gets an EPIPE on its next write, prints grep: write error: Broken pipe, and exits with code 2. Under pipefail, this non-zero exit code propagates and fails the entire workflow job.

Changes

1. Removed grep + head: Switched to native git tag filtering using the --list parameter.
2. Replaced with awk 'NR==1': Used awk 'NR==1' as the stream selector. Unlike head, awk 'NR==1' reads the entire stdin stream to completion (but only prints the first line). This prevents the writer (git tag) from encountering a closed pipe and guarantees a successful 0 exit code.

Summary by CodeRabbit

• Bug Fixes
  • Improved automated release workflows’ logic for selecting the newest valid version tag.
  • Added stricter semver-like tag matching and deterministic newest-tag sorting to ensure release creation and drift checks consistently use the correct tag.