Pin unsloth-zoo>=2026.6.5 in install.sh / install.ps1#6440
Merged
Conversation
The base-install lines passed a bare unsloth-zoo spec and relied on the co-installed unsloth>=2026.6.7 (whose pyproject pins unsloth_zoo>=2026.6.5) to floor unsloth-zoo transitively. Make the floor explicit so the install scripts stay in sync with pyproject and the bare spec can never resolve below the version that ships unsloth_zoo.diffusion_studio (the DiffusionGemma Studio runner), first released in unsloth-zoo 2026.6.4. Leaves the reinstall/upgrade flags and the git-main overlay untouched.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the installation scripts install.ps1 and install.sh to pin the minimum version of the unsloth-zoo package to >=2026.6.5 across various installation scenarios. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Pin the explicit
unsloth-zoospecs ininstall.shandinstall.ps1tounsloth-zoo>=2026.6.5, matching theunsloth_zoo>=2026.6.5floor already declared inpyproject.toml.Why
The base-install commands passed a bare
unsloth-zoo(no version) alongsideunsloth>=2026.6.7, relying on unsloth's transitive pin to floor unsloth-zoo. That works today, but the floor is implicit in the scripts and easy to drift frompyproject.toml.unsloth-zoo
2026.6.4is the first release that shipsunsloth_zoo.diffusion_studio(the DiffusionGemma runner used by Unsloth Studio). With an older unsloth-zoo, the Studio diffusion loader fails with "DiffusionGemma runner not found. Install unsloth_zoo (which ships unsloth_zoo.diffusion_studio.shim)...". Making the floor explicit keeps the install scripts and pyproject in lockstep and guarantees a diffusion-capable unsloth-zoo on every install path, not only via the transitive pin.Mirrors the approach in #5716 (keeping the install-script pins current).
Scope
unsloth-zoospecs in each script.--reinstall-package/--upgrade-packageflags and theunsloth-zoo @ git+...git-main overlay lines untouched.bash -n install.shpasses.Note
The normal end-user path already pulls a diffusion-capable unsloth-zoo transitively (pyproject pins
unsloth_zoo>=2026.6.5); this change makes that floor explicit and consistent across the install scripts as defense-in-depth.