Fix release pipeline: check remote for existing tag before pushing#149
Merged
JerrettDavis merged 1 commit intomainfrom Apr 20, 2026
Merged
Fix release pipeline: check remote for existing tag before pushing#149JerrettDavis merged 1 commit intomainfrom
JerrettDavis merged 1 commit intomainfrom
Conversation
Agent-Logs-Url: https://github.com/JerrettDavis/JD.Efcpt.Build/sessions/73c76567-33cf-4cb8-a527-b392c10dfbef Co-authored-by: JerrettDavis <2610199+JerrettDavis@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
JerrettDavis
April 20, 2026 15:55
View session
Copilot stopped work on behalf of
JerrettDavis due to an error
April 20, 2026 15:55
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.
Summary
The release pipeline was failing with:
Root Cause
The "Create and push git tag" step used
git rev-parse "v${PACKAGE_VERSION}"to check if a tag already existed — but this only checks local refs. If a previous run had already pushed the tag to the remote, but the current run's local repo didn't have that tag fetched, the check would pass and the push would be attempted, only to be rejected by the remote.Fix
Replaced
git rev-parsewithgit ls-remote --exit-code --tags origin "refs/tags/v${PACKAGE_VERSION}", which queries the remote directly. This correctly detects an already-existing remote tag and skips the push.