ci(release): fix actions/checkout fetch-tags conflict on push-tag#11
Merged
Sunrisepeak merged 1 commit intomainfrom May 8, 2026
Merged
ci(release): fix actions/checkout fetch-tags conflict on push-tag#11Sunrisepeak merged 1 commit intomainfrom
Sunrisepeak merged 1 commit intomainfrom
Conversation
The push-tag trigger that fired for v0.0.2 failed with Cannot fetch both ef6dffd... and refs/tags/v0.0.2 to refs/tags/v0.0.2 — a known interaction in actions/checkout@v4 where `fetch-tags: true` combined with a tag ref tries to fetch the same ref twice. Switching to `fetch-depth: 0` gives the resolve-tag step the full history it needs without the duplicate-fetch conflict. (The release.yml flow itself is unchanged; this only fixes the runner side.)
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
The v0.0.2 push-tag triggered run 25579775799 failed at the checkout step:
Known issue with
actions/checkout@v4when both the ref'd tag andfetch-tags: trueare set on the same checkout — it ends up trying tofetch the same ref twice. Switching to
fetch-depth: 0gives theresolve-tag step the full history it needs without the conflict.
Test plan
After merge:
gh workflow run release.yml -f tag=v0.0.2to rebuild v0.0.2 withthe fixed checkout step.