fix: delete local tag before creating for force release #76
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
When using "Force release even if version unchanged", the workflow deletes the remote tag but not the local tag. This causes the `git tag -a` command to fail with "tag already exists". Added `git tag -d` before creating the tag to handle force releases. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
There was a problem hiding this comment.
Pull request overview
This PR fixes a workflow failure that occurred when using the "Force release even if version unchanged" option. The issue was that while the remote tag was being deleted, the local tag remained, causing the tag creation to fail with "tag already exists".
Key changes:
- Added deletion of local git tag before creating a new one during force release
Code Coverage Report ❌Current coverage: 18.43% |
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.
Summary
Fix release workflow failure when using "Force release even if version unchanged".
Problem
When using the force release option, the workflow:
Error from failed run:
Solution
Added
git tag -d "$TAG_NAME" 2>/dev/null || truebefore creating the new tag.This matches the ULPB-iOS release workflow behavior.
Reference
🤖 Generated with Claude Code