bankjaneo/caprine v2.62.0

on GitHub

Release Note

• Feature: modern macOS window design — Apple Silicon builds now ship Electron 43, so macOS 26/27 (including the new Liquid Glass traffic-light buttons in macOS 27 Golden Gate) render natively
• Feature: maximum compatibility kept — Intel mac builds intentionally stay on the Electron 29 runtime with the macOS 10.15 floor unchanged, so Catalina and Big Sur users keep working
• Fix: window dragging on macOS — on some macOS versions and window-management setups the app couldn't be moved by dragging the top strip (it either never moved or stopped mid-drag, issue #41); a JS fallback now moves the window whenever the native drag gesture fails, with no change to normal dragging
• Fix: auto-update now points at this fork (bankjaneo/caprine) instead of the upstream repository, and releases now ship update manifests (latest-mac.yml, latest.yml, latest-linux.yml) — Windows and Linux AppImage builds can now update in place (macOS also needs code signing before in-app updates can work, see below)
• Chore: Windows and Linux builds bumped to Electron 43 (2 years of Chromium/security updates)
• Chore: differential (partial) update downloads enabled via blockmaps for macOS and Windows
• Chore: new CI check keeps mainline code compatible with both Electron 29 (Intel runtime) and Electron 43 (Apple Silicon runtime)

About auto-update

• Windows: install this release once manually — from the next release onward, the app updates itself automatically.
• Linux AppImage: install this release once manually — from the next release onward, the app updates itself automatically.
• macOS (Intel and Apple Silicon): in-app auto-update requires the app to be signed, which is not available yet — for now, update by downloading new releases manually. Install this release once to switch the updater to this fork; once signing is set up in a future release, updates will start working automatically.
• Linux deb/rpm/pacman: no in-app auto-update; update via the package repositories (deb also on Gemfury).
• Existing installs from before 2.62.0 still look for updates in the old upstream location, so none of the above takes effect until this release is installed once.

For macOS user

If macOS reports that "Caprine.app is damaged and can't be opened", that might be due to macOS gatekeeper flagged the download. Try running following commands in Terminal and open the app again.

xattr -l /Applications/Caprine.app
xattr -dr com.apple.quarantine /Applications/Caprine.app

Eliminating this step and getting in-app auto-update working on macOS requires an Apple Developer Program membership ($99/year). If you'd like to help make that happen, you can support me here: