Bump install.sh / install.ps1 pins to unsloth>=2026.8.22 - #9868
Merged
Merged
Conversation
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
2 participants
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.
Follows the release of
unsloth2026.8.22 to PyPI, moving the installer pins forward. Same shape as #5716.unsloth>=2026.8.21->unsloth>=2026.8.22(1 occurrence in each script, the_unsloth_release_install_spec/$_unslothReleaseInstallSpecdefault)unsloth-zoo>=2026.8.15->unsloth-zoo>=2026.8.16(5 occurrences in each script)2026.8.16is the current publishedunsloth_zooon PyPI, and it is whatpyproject.tomlalready declares, so the installers were the only place still asking for2026.8.15.The diff is 12 lines across the two files and touches nothing but the version strings.
bash -n install.shand a PowerShell parse ofinstall.ps1both pass.