fix: compute server release versions from tags
Merged
MO
8mo ago+146+146+012345678901234567890123456789-36-36-01234567890123456789
Compute server-v3 and server-v4 release versions from the latest server tag plus changeset bumps, instead of recomputing from package.json.
Summary by cubic
Compute next server release versions for v3 and v4 from the latest git tag plus changeset bumps, instead of package.json. This keeps release tags consistent and avoids version drift.
- Bug Fixes
- Parse changed
.changeset/*.mdsince the laststagehand-server-v3/v*orstagehand-server-v4/v*tag to find the highest bump for@browserbasehq/stagehand-server-v3and@browserbasehq/stagehand-server-v4. - Increment the tagged version (major/minor/patch), default to
0.0.0if no tag, removechangeset status/changeset-status.json, and outputrelease,version, and tag.
- Parse changed