Repository navigation
Conversation
Floating tags cause `git fetch` failures ("would clobber existing tag")
for anyone with a local clone. Branches are expected to move, so
`git fetch` updates them silently.
GitHub Actions resolves `@v1` identically whether it's a tag or branch,
so consuming repos are unaffected.
Co-Authored-By: Claude <noreply@anthropic.com>
tend-agent
approved these changes
Mar 25, 2026
tend-agent
pushed a commit
that referenced
this pull request
Mar 25, 2026
The shallow clone (default fetch-depth: 1) causes git push to fail with "remote contains work that you do not have locally" because the local repo can't prove the fast-forward to the remote without full history. This broke the v1 auto-update after PR #55 merged, keeping v1 stuck at fbf397e while main advanced. As a result, the compat fix in PR #54 cannot reach adopters even after merge. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Mar 25, 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.
Floating tags cause
git fetchfailures ("would clobber existing tag") for anyone with a local clone. Switches to a branch, which is the convention for GitHub Actions major-version refs (actions/checkout@v4is a branch). GitHub Actions resolves@v1identically either way.The remote
v1tag has been deleted and replaced with av1branch already — this PR updates the workflow to push to the branch instead of force-pushing a tag.