Alan Wizemann 679dedf132 fix: release script — push main + tag before gh release create ...

The script was creating the GitHub release before pushing main, which
caused gh to auto-create the v<VERSION> tag at the then-current origin
HEAD (one commit behind the bump, since main hadn't been pushed yet).
The subsequent `git push origin v<VERSION>` was then rejected as
non-fast-forward, leaving the remote tag pointing at the wrong commit.

Caught during v1.6.2. The remote tag for v1.6.2 was force-corrected to
12610fa (the bump commit); the release artifacts themselves were always
correct.

New order: push main → tag main locally → push tag → gh release create.
Gh will now find the tag already on origin and attach to the right
commit. Non-destructive: a retry-safe release can always be resumed.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-04-17 17:24:31 -07:00

..

ExportOptions.plist

feat: Sparkle auto-updates + Developer ID notarization pipeline

2026-04-16 18:42:20 -07:00

release.sh

fix: release script — push main + tag before gh release create

2026-04-17 17:24:31 -07:00