mirror of
https://github.com/storytold/craft-launcher.git
synced 2026-11-02 08:40:01 +00:00
307efcf45a
* feat(install): choose where Craft apps are installed Settings gets a default install folder, and a fresh install asks for the app's folder (prefilled with the default). Updates stay beside the copy they replace. Works for MSI (INSTALLFOLDER), DMG bundles, and AppImages; on Linux a custom folder means AppImage. Flatpak and the web build keep the system location and skip the prompt. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(windows): integrate portable installs with custom locations * fix(install): ask before writing over something already in the install folder Staging used a predictable `.<name>.partial` path beside the destination, so a file the user kept under that name could be overwritten (AppImage) or deleted (macOS). Stage in a fresh private folder instead. A new install whose destination already exists now stops before downloading and asks "Replace what's there?". Replace installs over it: the AppImage or .app is swapped in, a portable install writes over same-named files only, and the MSI installs into the existing folder. Cancel leaves everything as it was. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(install): a planted .partial symlink can't redirect AppImage staging Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Skyfuller1303 <skyfullerdesign@gmail.com>