Update safetensors-mojo to 0.8.0 for Mojo 1.1.0 - #360
Merged
alisterburt merged 1 commit intoSep 19, 2026
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
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.
Updates
safetensors-mojoto 0.8.0 for Mojo 1.1.0. Pinsmojo-compiler ==1.1.0in build, host, and run requirements because the package distributes a compiler-version-specific.mojocfile. The public API is unchanged.Validation: native
linux-64recipe build and installed-package smoke test passed with Mojo 1.1.0. Recipe rendering also passed forlinux-aarch64andosx-arm64.The published 0.7.0 build-0 packages declare
mojo-compiler >=1.0.0,<2.0a0, but their precompiled files require Mojo 1.0.0. Could the channel metadata for those variants on all three platforms be corrected tomojo-compiler ==1.0.0? This recipe update fixes new builds only; it does not correct the existing 0.7.0 records.Checklist