fix(ci): handle new tags in server release workflow (#1660)
Merged
MI
10mo ago+2+2+0123456789-1-1-0123456789
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.