Installer currently uses uv pip install to install Invoke, which results in locked dependencies from pyproject.toml like "compel==2.1.1", and latest like "accelerate". The reason is that uv pip is an affordance for migrating to uv from pip and keeps pip semantics, including not knowing about uv.lock. This results in Launcher installed InvokeAI installations being slightly different depending on the timing of the installation and what versions of packages were available on pypi.org at the time of the install.
The solution is to change from uv pip to uv sync.
Additionally I see uv is pinned to 0.6.12 here, which is over a year old and fails to parse my ~/.config/uv/uv.toml. I recommend upgrading uv to latest.
Installer currently uses
uv pip installto install Invoke, which results in locked dependencies from pyproject.toml like"compel==2.1.1",and latest like"accelerate". The reason is thatuv pipis an affordance for migrating to uv from pip and keeps pip semantics, including not knowing aboutuv.lock. This results in Launcher installed InvokeAI installations being slightly different depending on the timing of the installation and what versions of packages were available on pypi.org at the time of the install.The solution is to change from
uv piptouv sync.Additionally I see uv is pinned to
0.6.12here, which is over a year old and fails to parse my~/.config/uv/uv.toml. I recommend upgrading uv to latest.