fix: resolve server release versions from remote tags
Merged
MO
8mo ago+184+184+012345678901234567890123456789-16-16-01234567890123456789
Resolve server-v3 and server-v4 release versions from remote tags, fail instead of bootstrapping from 0.0.0, and refuse to publish any version that does not advance the highest existing remote tag.
Summary by cubic
Resolve release versions for @browserbasehq/stagehand-server-v3 and @browserbasehq/stagehand-server-v4 from remote Git tags and add guardrails to stop non-advancing or bootstrapped releases. Workflows fail if no remote release tag exists.
- Bug Fixes
- Determine latest remote tag with
git ls-remote --tags(no local tag reliance). - Fetch the resolved tag before diffing and ignore deleted changeset files.
- Require the computed version to advance the highest remote version; otherwise fail.
- Fail when no remote tag is found (no
0.0.0bootstrap).
- Determine latest remote tag with