fix(ci): handle new tags in server release workflow (#1660)

[miguelg719]

why

The git fetch command was failing with exit code 128 when trying to fetch a tag that doesn't exist on the remote yet (which is the case for new releases). This caused the entire release workflow to fail.

what changed

Added || true to allow the fetch to fail gracefully for new tags. The subsequent git rev-parse correctly handles both cases:

• Existing tag: script exits with "Tag already exists" message
• New tag: script proceeds to create and push the new tag

test plan

---

Summary by cubic

Prevented the server release workflow from failing on new releases by letting git fetch ignore missing remote tags. Existing tags exit with a clear message; new tags proceed to be created and pushed.

^{Written for commit d71339d. Summary will update on new commits. Review in cubic}

[changeset-bot]

⚠️ No Changeset found

Latest commit: d71339d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

[greptile-apps]

Greptile Overview

Greptile Summary

Fixed git fetch failure for new tags in the server release workflow by adding graceful error handling.

• Added || true to allow git fetch to fail without stopping the workflow when fetching tags that don't exist on the remote yet
• Redirected stderr to /dev/null to suppress error messages for expected failures
• The subsequent git rev-parse check correctly handles both existing and new tags, ensuring proper workflow behavior

Confidence Score: 5/5

• This PR is safe to merge with no risk
• The fix is minimal, well-understood, and directly addresses the exit code 128 error. The logic properly handles both existing and new tags with no side effects.
• No files require special attention

Important Files Changed

Filename	Overview
.github/workflows/stagehand-server-release.yml	Added graceful failure handling for git fetch when tag doesn't exist remotely, fixing exit code 128 errors for new releases

Sequence Diagram

sequenceDiagram
    participant GHA as GitHub Actions
    participant Git as Git Commands
    participant Remote as Remote Repository
    participant Local as Local Repository

    GHA->>Git: Configure git user
    Git->>Local: Set user.name and user.email
    
    GHA->>Git: Fetch tag from remote
    Git->>Remote: git fetch --force origin "refs/tags/${TAG}:refs/tags/${TAG}"
    
    alt Tag exists on remote
        Remote-->>Git: Tag found
        Git-->>Local: Update local tag reference
        Git-->>GHA: Success (exit 0)
    else Tag doesn't exist on remote (new release)
        Remote-->>Git: Error 128 (tag not found)
        Note over Git: 2>/dev/null suppresses error message
        Note over Git: || true converts exit code to 0
        Git-->>GHA: Success (exit 0)
    end
    
    GHA->>Git: Check if tag exists locally
    Git->>Local: git rev-parse -q --verify "refs/tags/${TAG}"
    
    alt Tag exists locally
        Local-->>Git: Tag found
        Git-->>GHA: Tag exists
        GHA->>GHA: Exit (no action needed)
    else Tag doesn't exist locally
        Local-->>Git: Tag not found
        Git-->>GHA: Tag doesn't exist
        GHA->>Git: Create new tag
        Git->>Local: git tag -a "${TAG}" "${TARGET_SHA}"
        GHA->>Git: Push tag to remote
        Git->>Remote: git push origin "${TAG}"
        Remote-->>Git: Tag pushed successfully
        Git-->>GHA: Success
    end

Loading

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}