maziggy 9c7e6a7b2c fix(updates): add --force to git fetch so re-pointed remote tags don't fail the update ...

In-app updater was failing on installs whose local clone had stale
  tags (e.g. v0.2.1 re-pointed upstream after a post-release re-tag).
  git fetch --prune --tags returns a non-zero exit when even one tag
  would be clobbered, even though origin/main and the target release
  tag itself fetched cleanly:

    ! [rejected] v0.2.1 -> v0.2.1 (would clobber existing tag)
    ...
    ERROR Git fetch failed: From https://github.com/maziggy/bambuddy

  The updater surfaced this as "Failed to fetch updates" and aborted,
  leaving the user stuck on the previous release.

  Adding --force lets the moved tag overwrite the local stale copy.
  That matches the in-app updater's contract ("sync me to the remote")
  and is what the native update.sh sidesteps entirely by not using
  --tags at all. The in-app path can't drop --tags because release-tag
  refs (v0.2.4b1, v0.2.4.1, etc.) need to be resolvable locally for the
  subsequent git reset --hard.

  Regression test asserts --force is in the fetch args alongside the
  existing --tags assertion.

2026-05-16 15:04:44 +02:00

..

app

fix(updates): add --force to git fetch so re-pointed remote tags don't fail the update

2026-05-16 15:04:44 +02:00

tests

fix(updates): add --force to git fetch so re-pointed remote tags don't fail the update

2026-05-16 15:04:44 +02:00

__init__.py

…