Repository navigation
fix(release): avoid SIGPIPE in changelog generation for long ranges - #559
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Generate changelog step piped git log into head -100 under pipefail. For the stable range (v0.10.5..HEAD, 116 commits) head closes the pipe early, git log gets SIGPIPE and the step exits 141 (dry run 39145997677). Use git log -n 100 instead of the pipe.
Other early-exit pipes reviewed and left unchanged: release.yml git show ... | head -1 (catalog TSV headers, 4-31 KB, below the pipe buffer so git finishes writing before head exits) and publish.yml echo "$TAG" | grep -q (tiny input).