Skip to content

v0.2.0 — macOS and Linux

Choose a tag to compare

View all tags
@TeeJS TeeJS released this 12 Sep 03:22
· 33 commits to main since this release
v0.2.0
5b5388d

git-updater now runs on macOS and Linux as well as Windows.

That is the whole of this release. The app does the same job it always did — keeps the software you picked up to date straight from its GitHub releases — on two more operating systems.

Get it

Download
Windows git-updater-0.2.0-x64.zip or -arm64.zip — unzip anywhere, run git-updater.exe
macOS git-updater-0.2.0-mac-arm64.dmg — open it, drag to Applications (Apple Silicon)
Linux git-updater-0.2.0-linux-x64.tar.gz or -arm64.tar.gz — extract and run

Windows builds are Authenticode-signed via Azure Trusted Signing. macOS builds are Developer ID signed, notarized and stapled.

An AppImage is also published. It needs libfuse2, which recent Ubuntu releases no longer install by default, so on many current systems it will not start unless libfuse2 is present. Where it is present the AppImage works normally. The tarball has no such requirement, which is why it is the recommended Linux download.

What is different per platform

  • macOS only manages notarized apps. That is Apple's rule, not ours: on Apple Silicon anything unnotarized is refused, including an app signed with a valid Developer ID. Downloads keep their quarantine flag, so an app you had previously approved by hand will ask again after an update.
  • macOS self-update reports rather than applies. An app bundle is the unit macOS launches, so there is nowhere to put a new version except on top of the running one. You get told a new version exists and sent here. Windows and Linux still update in place.
  • Linux does not scan for installed apps. Your package manager already owns most of what a scan would find, and installing a suggestion would give you a second copy outside it. Browsing the catalogue and adding apps by URL work as they always did.
  • Linux prefers a tarball over an AppImage when a project publishes both, for the reason above.

Safety

  • An update that would damage a macOS app's signature is rolled back and the working version restored, rather than leaving you with one that will not launch.
  • Archives keep their Unix permissions and symlinks, so extracted apps are actually runnable.
  • git-updater refuses to replace an app while it is running, on every platform.
Assets 10
Loading