fix: add retry logic for release PR detection in man page update#117
Merged
fix: add retry logic for release PR detection in man page update#117
Conversation
The previous workflow had a race condition where the man page update step would run immediately after release-plz created the PR, but before GitHub had fully propagated the PR labels. This fix adds: - Initial 5 second delay - Retry logic (3 attempts with 5 second delays) - Better logging for debugging Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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.
Summary
Adds retry logic to the man page update step in the release-plz workflow to handle GitHub API propagation delays.
Problem
In PR #115, we added a step to automatically regenerate man pages when release-plz creates a release PR. However, the step runs immediately after the PR is created, before GitHub has fully propagated the labels. This caused the
gh pr list --label releasecommand to return empty.This resulted in PR #116 (v1.0.15) being created without the man page regeneration, requiring manual intervention.
Solution
Test plan
🤖 Generated with Claude Code