chore: force-fetch tags in release script#17
Merged
sohil-kshirsagar merged 1 commit intomainfrom Mar 13, 2026
Merged
Conversation
jy-tan
approved these changes
Mar 13, 2026
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.
Adds
--forcetogit fetch --tagsin the release script.The release script force-updates the major version tag (e.g.
v1) on each release. This means anyone who isn't the last person to release will have a stale local tag. Without--force,git fetch --tagsrefuses to overwrite it, causing the script to fail with "would clobber existing tag".Summary by cubic
Force-fetch tags in the release script to overwrite stale local major tags (e.g., v1) and prevent "would clobber existing tag" failures. Adds
--forceto thegit fetch --tagscall inscripts/release.sh.Written for commit 702912a. Summary will update on new commits.