Bump install.sh / install.ps1 pin to unsloth>=2026.5.6 - #5716
Conversation
PyPI release 2026.5.6 is now live; update install.sh and install.ps1 to pin against the new minimum so fresh installs pick up the latest wheel.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the unsloth package version requirement from 2026.5.5 to 2026.5.6 across multiple installation paths in both the install.ps1 and install.sh scripts. The review feedback identifies inconsistencies in specific installation commands that are missing the --upgrade-package flag and use a package ordering that deviates from the established pattern in the rest of the codebase, potentially affecting update reliability and maintainability.
| substep "installing unsloth (this may take a few minutes)..." | ||
| if ($StudioLocalInstall) { | ||
| $baseInstallExit = Invoke-InstallCommand { uv pip install --python $VenvPython unsloth-zoo "unsloth>=2026.5.5" --torch-backend=auto } | ||
| $baseInstallExit = Invoke-InstallCommand { uv pip install --python $VenvPython unsloth-zoo "unsloth>=2026.5.6" --torch-backend=auto } |
There was a problem hiding this comment.
The uv pip install command in this fallback path is inconsistent with other installation paths in the script (e.g., line 1357). It lacks the --upgrade-package unsloth flag, which is important for ensuring the package is correctly updated during installation retries. Additionally, the package order is reversed compared to the established pattern in the rest of the module.
$baseInstallExit = Invoke-InstallCommand { uv pip install --python $VenvPython --upgrade-package unsloth "unsloth>=2026.5.6" unsloth-zoo --torch-backend=auto }
References
- Prioritize consistency with established coding patterns within a module.
| substep "installing unsloth (this may take a few minutes)..." | ||
| if [ "$STUDIO_LOCAL_INSTALL" = true ]; then | ||
| run_install_cmd "install unsloth (auto torch backend)" uv pip install --python "$_VENV_PY" unsloth-zoo "unsloth>=2026.5.5" --torch-backend=auto | ||
| run_install_cmd "install unsloth (auto torch backend)" uv pip install --python "$_VENV_PY" unsloth-zoo "unsloth>=2026.5.6" --torch-backend=auto |
There was a problem hiding this comment.
The uv pip install command in this fallback path is inconsistent with other installation paths in the script (e.g., line 2059). It is missing the --upgrade-package unsloth flag, which ensures the package is updated during retries. The package order should also be aligned with the pattern used in other hunks for better maintainability.
| run_install_cmd "install unsloth (auto torch backend)" uv pip install --python "$_VENV_PY" unsloth-zoo "unsloth>=2026.5.6" --torch-backend=auto | |
| run_install_cmd "install unsloth (auto torch backend)" uv pip install --python "$_VENV_PY" --upgrade-package unsloth "unsloth>=2026.5.6" unsloth-zoo --torch-backend=auto |
References
- Prioritize consistency with established coding patterns within a module.
PyPI release 2026.5.6 is now live; update install.sh and install.ps1 to pin against the new minimum so fresh installs pick up the latest wheel. Co-authored-by: Michael Han <michaelhan2050@gmail.com>
…oo>=2026.7.2 (#6981) PyPI release unsloth 2026.7.2 is now live. Bumps the pinned floor in install.sh and install.ps1 from 2026.7.1 to 2026.7.2 for both unsloth and unsloth-zoo across all 5 install commands (no-torch / reinstall / upgrade / local / auto torch backend paths) so fresh installs resolve to the new wheel. Follows the same pattern as #5716.
2 participants
Summary
install.shandinstall.ps1fromunsloth>=2026.5.5tounsloth>=2026.5.6so fresh installs resolve to the new wheel.v0.1.415-beta.Test plan
install.shon a clean Linux hostinstall.ps1on a clean Windows hostuv pip install "unsloth>=2026.5.6"resolves cleanly