Skip to content

fix: use v1 branch instead of floating tag - #55

Merged
max-sixty merged 1 commit into
mainfrom
tag
Mar 25, 2026
Merged

max-sixty merged 1 commit into
mainfrom
tag

Conversation

@max-sixty

Copy link
Copy Markdown
Owner

Floating tags cause git fetch failures ("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@v4 is a branch). GitHub Actions resolves @v1 identically either way.

The remote v1 tag has been deleted and replaced with a v1 branch already — this PR updates the workflow to push to the branch instead of force-pushing a tag.

This was written by Claude Code on behalf of @max-sixty

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>
@max-sixty
max-sixty merged commit 62ae89c into main Mar 25, 2026
3 checks passed
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants