fix: fetch tags in agent checkout before computing next release version - #273
Merged
Merged
Conversation
…rkflow The agent checkout uses fetch-depth: 1 with no tag fetching, so `git tag --list` returned empty, falling back to v0.0.0. The AI then computed v0.0.1 as the next patch release, but that tag already existed. Fix: add `git fetch --tags` before the tag listing command and switch to `sort -V` (shell version sort) which is more reliable than git's `--sort=-version:refname` in container environments. Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
fix: fetch tags before computing release version in create-release workflow
fix: fetch tags in agent checkout before computing next release version
Jul 29, 2026
Copilot created this pull request from a session on behalf of
pelikhan
July 29, 2026 08:30
View session
pelikhan
marked this pull request as ready for review
July 29, 2026 08:30
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.
The
create_releasejob was failing withfatal: tag 'v0.0.1' already existsbecause the agent runs in a shallow checkout (fetch-depth: 1) with no tags.git tag --listreturned nothing, the fallbackv0.0.0kicked in, and the AI dutifully computedv0.0.1— a tag that already existed.Changes
create-release.mdStep 1: addgit fetch --tagsbefore the tag listing command; replacegit tag --sort=-version:refname | head -n 1withsort -V | tail -n 1(more portable across git versions and container environments)create-release.lock.yml: recompiled viagh aw compile create-release --strict