Releases: invoke-ai/launcher
1.8.1
This patch release updates an internal dependency.
How to Install
As of v1.7.0, the Launcher will keep itself updated. You only need to follow the below instructions if it's your first time installing the Launcher.
Windows
- Click here to download the latest Launcher setup
EXEfor Windows. - Run the
EXEto install the Launcher and start it. - A desktop shortcut will be created; use this to run the Launcher in the future.
- You can delete the
EXEfile you downloaded.
macOS
- Click here to download the latest Launcher
DMGfor macOS. - Open the
DMGand drag the app intoApplications. - Run the Launcher using its entry in
Applications.
Linux
- Click here to download the latest Launcher
AppImagefor Linux. - You may need to edit the
AppImagefile properties and make it executable. - Optionally move the file to a location that does not require admin privileges and add a desktop shortcut for it.
- Run the Launcher by double-clicking the
AppImageor the shortcut you made.
What's Changed
- chore: point ui lib dep to gh by @psychedelicious in #119
- chore: bump version to v1.8.1 by @psychedelicious in #120
Full Changelog: v1.8.0...v1.8.1
1.8.0
This release adds a link to the release notes when an Invoke update is available, after you choose the version to install.
How to Install
As of v1.7.0, the Launcher will keep itself updated. You only need to follow the below instructions if it's your first time installing the Launcher.
Windows
- Click here to download the latest Launcher setup
EXEfor Windows. - Run the
EXEto install the Launcher and start it. - A desktop shortcut will be created; use this to run the Launcher in the future.
- You can delete the
EXEfile you downloaded.
macOS
- Click here to download the latest Launcher
DMGfor macOS. - Open the
DMGand drag the app intoApplications. - Run the Launcher using its entry in
Applications.
Linux
- Click here to download the latest Launcher
AppImagefor Linux. - You may need to edit the
AppImagefile properties and make it executable. - Optionally move the file to a location that does not require admin privileges and add a desktop shortcut for it.
- Run the Launcher by double-clicking the
AppImageor the shortcut you made.
What's Changed
- feat: add link to release notes in install flow by @psychedelicious in #116
- chore: bump version to v1.8.0 by @psychedelicious in #117
Full Changelog: v1.7.1...v1.8.0
1.7.1
This release fixes an issue where environment variables were not used when installing and running Invoke.
For example, env vars set in .zshrc on macOS to configure uv download mirrors weren't used. They will be seen now, as the Launcher uses the user shell env when installing.
Similarly, when running Invoke, the user's shell env is merged in, allowing you to configure Invoke by setting INVOKEAI_ env vars.
How to Install
As of v1.7.0, the Launcher will keep itself updated. You only need to follow the below instructions if it's your first time installing the Launcher.
Windows
- Click here to download the latest Launcher setup
EXEfor Windows. - Run the
EXEto install the Launcher and start it. - A desktop shortcut will be created; use this to run the Launcher in the future.
- You can delete the
EXEfile you downloaded.
macOS
- Click here to download the latest Launcher
DMGfor macOS. - Open the
DMGand drag the app intoApplications. - Run the Launcher using its entry in
Applications.
Linux
- Click here to download the latest Launcher
AppImagefor Linux. - You may need to edit the
AppImagefile properties and make it executable. - Optionally move the file to a location that does not require admin privileges and add a desktop shortcut for it.
- Run the Launcher by double-clicking the
AppImageor the shortcut you made.
What's Changed
- chore: prep for v1.7.0 by @psychedelicious in #106
- build: copy artifacts, replacing the version number with latest in name by @psychedelicious in #107
- build: try again for "latest" artifacts by @psychedelicious in #108
- docs: update readme by @psychedelicious in #109
- feat: use
shell-envto grab user-defined env vars when running Launcher as GUI app by @psychedelicious in #112
Full Changelog: v1.7.0...v1.7.1
1.7.0
This release includes a number of QoL improvements, including Launcher self-updates and improved memory usage, resolving crashes with a message like Process exited with signal SIGTERM.
How to Install
The Launcher will let you know when it has an update for itself. You only need to follow the below instructions if it's your first time installing the Launcher.
Windows
- Click here to download the latest Launcher setup
EXEfor Windows. - Run the
EXEto install the Launcher and start it. - A desktop shortcut will be created; use this to run the Launcher in the future.
- You can delete the
EXEfile you downloaded.
macOS
- Click here to download the latest Launcher
DMGfor macOS. - Open the
DMGand drag the app intoApplications. - Run the Launcher using its entry in
Applications.
Linux
- Click here to download the latest Launcher
AppImagefor Linux. - You may need to edit the
AppImagefile properties and make it executable. - Optionally move the file to a location that does not require admin privileges and add a desktop shortcut for it.
- Run the Launcher by double-clicking the
AppImageor the shortcut you made.
Changes
Windows uses an Installer
The file Windows users download from GH releases is now an installer for the Launcher - not a portable EXE.
When you first run the EXE, the Launcher will be installed and a desktop shortcut created. Use the desktop shortcut to run the Launcher. You can then delete the EXE you downloaded.
macOS builds are signed
The xattr workaround is no longer necessary to run the Launcher on macOS.
Launcher Auto-Update
This should be the last Launcher version you need to download and run manually! 😎
On startup, the Launcher now checks once to see if there are any updates available. If an update is available, you will be prompted to download the update.
The download happens in the background. Once it finishes, you will be prompted to restart and install the update.
There's a new setting to opt-in to Launcher prereleases, disabled by default. If the setting is enabled, the Launcher will check for prerelease versions (e.g. alphas like this one).
SIGTERM Crashes
A common issue with the Launcher were crashes accompanied by a message like Process exited with signal SIGTERM.
These crashes were related to excessive memory usage by the Launcher and are resolved in this release.
Enhancements
- On Windows, the Launcher is now distributed as an installer instead of a portable executable.
- On macOS, the Launcher is now signed. macOS should not tell you it is damaged, and you should not need to manually clear the quarantine flag with
xattr. - Improvements to memory management of the Launcher, resolving Invoke crashes accompanied by a message like
Process exited with signal SIGTERM. - The Install and Launch log viewers are now both
xtermjsinstances, improving log output (progress bars!) and reducing memory usage. - Smaller builds thanks to an optimization of the build pipeline.
- If the UI Window crashes but the server is still running, you will be able to re-open the window and pick up where you left off.
Fixes
- Fix a minor memory leak related to
xtermjsinstances not being disposed properly. Would only be an issue if users repeatedly created and exited the dev console.
Internal
- Update all dependencies to latest.
- Migrate from
electron-forge+electron-builderfranken-pipeline toelectron-vite+electron-builder. New build process. - Move codesigning to this repo (previously was done in a private repo), sign macOS builds in CI.
- General spruce-up of CI workflows.
- Major internal refactors to reduce complexity of process management and support
xtermjsas the default log viewer.
What's Changed
- chore: package updates & general maintenance by @psychedelicious in #83
- feat: suite of memory usage improvements by @psychedelicious in #84
- ci: integrate windows codesigning in repo by @psychedelicious in #85
- ci: add separate workflow to build and sign by @psychedelicious in #86
- ci: fix env vars for macos sign by @psychedelicious in #87
- experiment: use electron-vite for build & electron-builder for packaging by @psychedelicious in #89
- ci: faster workflows by @psychedelicious in #90
- chore: v1.7.0a1 by @psychedelicious in #91
- feat: virtualized log viewer by @psychedelicious in #92
- feat: xterm log viewer & v1.7.0a3 by @psychedelicious in #93
- feat: launcher auto-update by @psychedelicious in #94
- chore: bump version to v1.7.0-alpha.8 by @psychedelicious in #95
- fix: setting typo opt in to launcher prereleases by @psychedelicious in #96
- build stuff by @psychedelicious in #97
- fix: windows-specific fixes by @psychedelicious in #98
- feat: safe exiting by @psychedelicious in #99
- fix: blank windows on close on Windows by @psychedelicious in #100
- chore: spruce up release process by @psychedelicious in #101
- ci: run build and sign jobs on tag push by @psychedelicious in #102
- chore: bump version to v1.7.0-alpha.12 by @psychedelicious in #103
- ci: ignore version changes when hashing lockfile by @psychedelicious in #104
- chore: v1.7.0-beta.1 by @psychedelicious in #105
Full Changelog: v1.6.0...v1.7.0
1.7.0-beta.1
This minor release includes a number of QoL improvements, including Launcher self-updates and improved memory usage, resolving crashes with a message like Process exited with signal SIGTERM.
Windows uses an Installer
The file Windows users download from GH releases is now an installer for the Launcher - not a portable EXE.
When you first run the EXE, the Launcher will be installed and a desktop shortcut created. Use the desktop shortcut to run the Launcher. You can then delete the EXE you downloaded.
macOS builds are signed
The xattr workaround is no longer necessary to run the Launcher on macOS.
Launcher Auto-Update
This should be the last Launcher version you need to download and run manually! 😎
On startup, the Launcher now checks once to see if there are any updates available. If an update is available, you will be prompted to download the update.
The download happens in the background. Once it finishes, you will be prompted to restart and install the update.
There's a new setting to opt-in to Launcher prereleases, disabled by default. If the setting is enabled, the Launcher will check for prerelease versions (e.g. alphas like this one).
SIGTERM Crashes
A common issue with the Launcher were crashes accompanied by a message like Process exited with signal SIGTERM.
These crashes were related to excessive memory usage by the Launcher and are resolved in this release.
Enhancements
- On Windows, the Launcher is now distributed as an installer instead of a portable executable.
- On macOS, the Launcher is now signed. macOS should not tell you it is damaged, and you should not need to manually clear the quarantine flag with
xattr. - Improvements to memory management of the Launcher, resolving Invoke crashes accompanied by a message like
Process exited with signal SIGTERM. - The Install and Launch log viewers are now both
xtermjsinstances, improving log output (progress bars!) and reducing memory usage. - Smaller builds thanks to an optimization of the build pipeline.
- If the UI Window crashes but the server is still running, you will be able to re-open the window and pick up where you left off.
Fixes
- Fix a minor memory leak related to
xtermjsinstances not being disposed properly. Would only be an issue if users repeatedly created and exited the dev console.
Internal
- Update all dependencies to latest.
- Migrate from
electron-forge+electron-builderfranken-pipeline toelectron-vite+electron-builder. New build process. - Move codesigning to this repo (previously was done in a private repo), sign macOS builds in CI.
- General spruce-up of CI workflows.
- Major internal refactors to reduce complexity of process management and support
xtermjsas the default log viewer.
What's Changed
- chore: package updates & general maintenance by @psychedelicious in #83
- feat: suite of memory usage improvements by @psychedelicious in #84
- ci: integrate windows codesigning in repo by @psychedelicious in #85
- ci: add separate workflow to build and sign by @psychedelicious in #86
- ci: fix env vars for macos sign by @psychedelicious in #87
- experiment: use electron-vite for build & electron-builder for packaging by @psychedelicious in #89
- ci: faster workflows by @psychedelicious in #90
- chore: v1.7.0a1 by @psychedelicious in #91
- feat: virtualized log viewer by @psychedelicious in #92
- feat: xterm log viewer & v1.7.0a3 by @psychedelicious in #93
- feat: launcher auto-update by @psychedelicious in #94
- chore: bump version to v1.7.0-alpha.8 by @psychedelicious in #95
- fix: setting typo opt in to launcher prereleases by @psychedelicious in #96
- build stuff by @psychedelicious in #97
- fix: windows-specific fixes by @psychedelicious in #98
- feat: safe exiting by @psychedelicious in #99
- fix: blank windows on close on Windows by @psychedelicious in #100
- chore: spruce up release process by @psychedelicious in #101
- ci: run build and sign jobs on tag push by @psychedelicious in #102
- chore: bump version to v1.7.0-alpha.12 by @psychedelicious in #103
- ci: ignore version changes when hashing lockfile by @psychedelicious in #104
Full Changelog: v1.6.0...v1.7.0-beta.1
v1.7.0-alpha.12
This release is identical to v1.7.0-alpha.11 release except the version number is bumped.
It is published so that we can test the Launcher's new auto-update functionality. Please see the v1.7.0-alpha.11 release notes for more information. No need to install this version explicitly.
v1.7.0-alpha.11
Testing this Alpha
This is the first Launcher release that can update itself. You can help to test this process:
- Download this prerelease (
v1.7.0-alpha.11) - Opt in to Launcher prereleases
- Restart the Launcher
- You should be prompted to update to
v1.7.0-alpha.12 - Download the update
- Restart when prompted to install the update
Since the last Alpha
- Fix a typo that broke Launcher prerelease update checking.
- Fix a number of Windows-specific issues (layout slightly off, blank windows appearing when exiting Invoke or closing dev console,
xtermjslog output resetting in certain situations, what appeared to be an error message after a normal shutdown of Invoke). - Internal changes to smooth out the release process.
Windows uses an Installer
The file Windows users download from GH releases is now an installer for the Launcher. When you first run it, the Launcher will be installed and a desktop shortcut created.
Use the desktop shortcut to run the Launcher. You can delete the EXE you downloaded..
Launcher Auto-Update
On startup, the Launcher now checks once to see if there are any updates available. If an update is available, you will be prompted to download the update.
The download happens in the background. Once it finishes, you will be prompted to restart and install the update.
There's a new setting to opt-in to Launcher prereleases, disabled by default. If the setting is enabled, the Launcher will check for prerelease versions (e.g. alphas like this one).
Enhancements
- On Windows, the Launcher is now distributed as an installer instead of a portable executable.
- On macOS, the Launcher is now signed. macOS should not tell you it is damaged, and you should not need to manually clear the quarantine flag with
xattr. - Improvements to memory management of the Launcher, resolving Invoke crashes accompanied by a message like
Process exited with signal SIGTERM. - The Install and Launch log viewers are now both
xtermjsinstances, improving log output (progress bars!) and reducing memory usage. - Smaller builds thanks to an optimization of the build pipeline.
- If the UI Window crashes but the server is still running, you will be able to re-open the window and pick up where you left off.
Fixes
- Fix a minor memory leak related to
xtermjsinstances not being disposed properly. Would only be an issue if users repeatedly created and exited the dev console.
Internal
- Update all dependencies to latest.
- Migrate from
electron-forge+electron-builderfranken-pipeline toelectron-vite+electron-builder. New build process. - Move codesigning to this repo (previously was done in a private repo), sign macOS builds in CI.
- General spruce-up of CI workflows.
- Major internal refactors to reduce complexity of process management and support
xtermjsas the default log viewer.
What's Changed
- chore: package updates & general maintenance by @psychedelicious in #83
- feat: suite of memory usage improvements by @psychedelicious in #84
- ci: integrate windows codesigning in repo by @psychedelicious in #85
- ci: add separate workflow to build and sign by @psychedelicious in #86
- ci: fix env vars for macos sign by @psychedelicious in #87
- experiment: use electron-vite for build & electron-builder for packaging by @psychedelicious in #89
- ci: faster workflows by @psychedelicious in #90
- chore: v1.7.0a1 by @psychedelicious in #91
- feat: virtualized log viewer by @psychedelicious in #92
- feat: xterm log viewer & v1.7.0a3 by @psychedelicious in #93
- feat: launcher auto-update by @psychedelicious in #94
- chore: bump version to v1.7.0-alpha.8 by @psychedelicious in #95
- fix: setting typo opt in to launcher prereleases by @psychedelicious in #96
- build stuff by @psychedelicious in #97
- fix: windows-specific fixes by @psychedelicious in #98
- feat: safe exiting by @psychedelicious in #99
- fix: blank windows on close on Windows by @psychedelicious in #100
- chore: spruce up release process by @psychedelicious in #101
Full Changelog: v1.6.0...v1.7.0-alpha.11
1.7.0-alpha.8
This release is identical to v1.7.0-alpha.7 release except the version number is bumped.
It is published so that we can test the Launcher's new auto-update functionality. Please see the v1.7.0-alpha.7 release notes for more information. No need to install this version explicitly.
1.7.0-alpha.7
Testing this Alpha
This is the first Launcher release that can update itself. You can help to test this process:
- Download this prerelease (
v1.7.0-alpha.7) - Opt in to Launcher prereleases
- Restart the Launcher
- You should be prompted to update to
v1.7.0-alpha.8 - Download the update
- Restart when prompted to install the update
Launcher Auto-Update
On startup, the Launcher now checks once to see if there are any updates available. If an update is available, you will be prompted to download the update.
The download happens in the background. Once it finishes, you will be prompted to restart and install the update.
There's a new setting to opt-in to Launcher prereleases, disabled by default. If the setting is enabled, the Launcher will check for prerelease versions (e.g. alphas like this one).
Enhancements
- On Windows, the Launcher is now distributed as an installer instead of a portable executable.
- On macOS, the Launcher is now signed. macOS should not tell you it is damaged, and you should not need to manually clear the quarantine flag with
xattr. - Improvements to memory management of the Launcher, resolving Invoke crashes accompanied by a message like
Process exited with signal SIGTERM. - The Install and Launch log viewers are now both
xtermjsinstances, improving log output (progress bars!) and reducing memory usage. - Smaller builds thanks to an optimization of the build pipeline.
- If the UI Window crashes but the server is still running, you will be able to re-open the window and pick up where you left off.
Fixes
- Fix a minor memory leak related to
xtermjsinstances not being disposed properly. Would only be an issue if users repeatedly created and exited the dev console.
Internal
- Update all dependencies to latest.
- Migrate from
electron-forge+electron-builderfranken-pipeline toelectron-vite+electron-builder. New build process. - Move codesigning to this repo (previously was done in a private repo), sign macOS builds in CI.
- General spruce-up of CI workflows.
- Major internal refactors to reduce complexity of process management and support
xtermjsas the default log viewer.
What's Changed
- chore: package updates & general maintenance by @psychedelicious in #83
- feat: suite of memory usage improvements by @psychedelicious in #84
- ci: integrate windows codesigning in repo by @psychedelicious in #85
- ci: add separate workflow to build and sign by @psychedelicious in #86
- ci: fix env vars for macos sign by @psychedelicious in #87
- experiment: use electron-vite for build & electron-builder for packaging by @psychedelicious in #89
- ci: faster workflows by @psychedelicious in #90
- chore: v1.7.0a1 by @psychedelicious in #91
- feat: virtualized log viewer by @psychedelicious in #92
- feat: xterm log viewer & v1.7.0a3 by @psychedelicious in #93
- feat: launcher auto-update by @psychedelicious in #94
Full Changelog: v1.6.0...v1.7.0-alpha.7
1.7.0-alpha.10
Test release for Launcher auto-updates.