Commit 653268b
# 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
<!-- This is an auto-generated description by cubic. -->
---
## 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.
<sup>Written for commit d71339d.
Summary will update on new commits. <a
href="https://cubic.dev/pr/browserbase/stagehand/pull/1661">Review in
cubic</a></sup>
<!-- End of auto-generated description by cubic. -->
Co-authored-by: Chromie <miguel@browserbase.com>
Co-authored-by: Chromie Bot <chromie@browserbase.com>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
1 parent 55b78b8 commit 653268b
1 file changed
+2
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
102 | 102 | | |
103 | 103 | | |
104 | 104 | | |
105 | | - | |
| 105 | + | |
| 106 | + | |
106 | 107 | | |
107 | 108 | | |
108 | 109 | | |
| |||
0 commit comments