fix(release): retry transient Gitee tag pushes - #856
Draft
haofeng0705 wants to merge 1 commit into
Draft
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
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.
What changed
Why
Recent Gitee repairs for
v1.0.55-beta.7andv1.0.56-beta.3passed GitHub release authority and artifact verification, but each made only one tag push. The push stalled until the old timeout and the repair failed without a safe retry.The new flow remains fail-closed: it never moves an existing tag and accepts a timed-out/concurrent push only when the remote tag resolves to the exact expected commit.
Validation
Result: PASS.